The overhead agent wraps 140+ MCP tools behind a single MCP server (pole-model-mcp). Tools are grouped here by category — with a catalog this size the list below is representative, not exhaustive. For full input / output schemas, point an MCP-aware client at the server and call the protocol’s list_tools.
Pole assembly & modification
Step-by-step or bulk pole construction. Crossarms, insulators, risers, guy anchors, equipment placement, comm-bundle overlashing, tap extensions. Replacement-pole cloning with auto-height adjustment. Covers transmission structures too — H-frame and tubular-steel monopole geometry alongside single-pole distribution.
Notable composites: build_pole_from_payload, build_replacement_pole, build_and_export_compliant_pole.
Clearance & compliance
CPUC GO-95 (Tables 1 & 2), NESC C2 (Tables 232, 235), and CSA C22.3 No.1 (Table 2 ground clearance + Table D.3 snow-depth) electrical clearance checks. Conductor sag analysis with temperature. Ground and conductor-separation violation detection, plus midspan separation at sag.
Notable composites: analyze_and_run_clearance, fix_clearance_violation.
Loading, framing & guying
Whole-line loading solves, weather-driven storm sweeps, multi-state sag-tension, framing classification/validation against utility-standard rules, and guying-strength checks against a master SPIDA guy/anchor catalog. Framing-first cascade auto-runs before assuming pole strength is the problem, and proposes guying fixes when that’s the real gap.
Version control (git-for-poles)
Every UPM snapshot is a commit; every physical pole has a pole-of-record. Tools cover the pole-of-record lifecycle (set / get / revert), work-order commit and analysis-aware merge (preview_pole_merge, commit_pole_merge, resolve_merge_conflict, mitigate_merge_conflict), line-section finalization, RUS Compatible-Unit BOM generation, and design-option branching for A/B comparison. See Concurrent work orders → for the full workflow.
Multi-format I/O
Parse SPIDA, O-Calc, PLS (with optional .loa), drone imagery, and field-capture data. Export SPIDA, frm-driven PLS-POLE bundles, catalog-free O-Calc, ESRI GeoJSON, Pixar USD, and Bentley iTwin/IFC BIS-schema payloads.
Notable composites: analyze_and_run_clearance, build_and_export_compliant_pole.
ESRI GIS sync
Push, pull, and sync pole models, attachment metadata, and conductor records to ESRI feature layers. Sync analysis results (clearance status, enrichment fields) back to existing features.
Joint-use, cost & BOM
NCJPA JP Form 2 analysis and rendering for single-pole and replacement-pair workflows. Installation and replacement-project cost estimates. Replacement-planning enrichment (construction costs, shared-facility flags). RUS Compatible-Unit-coded BOM for any set of proposed changes.
Span analysis
Static sag + lowest ground/span clearance for a named conductor span, pole-derived span direction with conductor-family fallback, and whole-line multi-span clearance sweeps. Stringing charts, staking reports, and make-ready report generation (clearance section, CU cost estimate, overlash diff).
Scenario state, USD & ML datasets
Named operating conditions (rain_peak, summer_load) with multi-family metadata (electrical, thermal, mechanical, connection-mechanics). Whole-line conductor-family shadow-swap with cascading re-validation. USD / USDA 3D scene assembly with a full component library. Tensor dataset generation in three projection modes — pole_tabular, attachment_sequence, connection_mechanics.
Standards review
Utility-specific RAG-backed review and Q&A with PDF ingestion. Cited findings across GO-95, NESC, CSA, RUS, and utility construction standards.
Underground bridge
bridge_risers_to_underground auto-seeds a connected vault record for a riser on an overhead pole — the one tool that stitches the overhead and underground domains together.
Standout features
- Composite operations that fold 3–5 steps into one call
- Analysis-aware merge for concurrent work orders on the same physical pole
- What-if conductor swaps with cascading strength re-checks, whole-line
- Same-circuit Q&A flow for Table 2 disambiguation
- 3D ghost rendering in USD with scenario metadata, plus IFC/BIS export for BIM
- Field-to-model capture from drone imagery and field-capture data
- Transmission-aware — H-frame and steel monopole structures alongside distribution poles
See also
- Overhead gateway → — the conversational layer that calls these tools
- Concurrent work orders → — the version-control workflow in depth
- Underground tool catalog →