Skip to main content
Glama
muend

arcgis-mcp-bridge

by muend
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

route_analysis

Find the best route through ordered stops for logistics, field visits, or travel-time analysis using ArcGIS Network Analyst.

Instructions

Solve the best route through ordered stop points using ArcPy Network Analyst MakeRouteAnalysisLayer. Use this for A-to-B routing, multi-stop field visits, logistics paths, inspection sequences, or travel-time analysis over a configured network dataset. Requires a Network Analyst license; reads stops and writes solved route features to out_features.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.6.3
    • addedInput schema / $defs / RouteAnalysisInput / description
      Added value: +"Input contract for solving routes through ordered stop points."
    • changedInput schema / $defs / RouteAnalysisInput / properties / network_dataset / description
      Previous value: -"Path to the network dataset."New value: +"Absolute path to the ArcGIS network dataset used for routing or accessibility analysis. The path must be inside a configured PathGuard allowed root and must be usable by ArcPy Network Analyst."
    • changedInput schema / $defs / RouteAnalysisInput / properties / out_features / description
      Previous value: -"Solved result feature class."New value: +"Absolute output feature class path to create with the solved network analysis result. Existing outputs require overwrite=true."
    • addedInput schema / $defs / RouteAnalysisInput / properties / overwrite / description
      Added value: +"Set true only when replacing an existing network analysis output feature class is intended."
    • changedInput schema / $defs / RouteAnalysisInput / properties / stops / description
      Previous value: -"Ordered point FC of route stops (A->B->...)."New value: +"Absolute path to an ordered point feature class of route stops, such as A-to-B or multi-stop stop sequences. The path must be inside a configured PathGuard allowed root."
    • changedInput schema / $defs / RouteAnalysisInput / properties / travel_mode / description
      Previous value: -"Named travel mode (e.g. 'Driving Time'); None = default."New value: +"Optional named travel mode from the network dataset, for example 'Driving Time' or 'Walking Time'. Use None to let ArcPy use the network dataset default travel mode."
  2. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description must convey behavioral traits. It states the tool requires a Network Analyst license, reads stops, and writes results to out_features. However, it does not detail side effects (e.g., whether inputs are modified) or behavior when overwrite is false. This is adequate but not rich.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences: first sentence defines the core function, second adds use cases and requirements. It is front-loaded and contains no redundant words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity and the presence of an output schema (not shown but noted), the description covers the routing workflow well. It lacks mention of output schema details, but those are provided elsewhere. Slightly incomplete in explaining the result format.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is high (0% description coverage but schema has detailed parameter descriptions). The description adds little beyond the schema, only reiterating the overall process. Baseline 3 is appropriate as the schema carries the semantic burden.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Solve the best route through ordered stop points using ArcPy Network Analyst MakeRouteAnalysisLayer.' This is a specific verb-resource pair, and it distinguishes the tool from siblings like closest_facility or od_cost_matrix.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description lists explicit use cases (A-to-B routing, multi-stop field visits, logistics paths, etc.) and notes licensing requirements. It does not explicitly state when not to use or compare with sibling tools, but the context is clear enough.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools