Skip to main content
Glama
muend

arcgis-mcp-bridge

by muend
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

feature_vertices_to_points

Extract vertices from line or polygon features as points for geometry inspection and quality checks. Supports all vertices, endpoints, or midpoints.

Instructions

Convert feature vertices to point features using ArcPy FeatureVerticesToPoints. Use this to extract endpoints, all vertices, midpoints, or dangle points from line or polygon geometry for QA/QC, network checks, and geometry inspection. Reads in_features and creates out_features inside PathGuard allowed roots.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.0.1
    • addedInput schema / $defs / FeatureVerticesToPointsInput / description
      Added value: +"Input contract for extracting vertices from features as points."
    • addedInput schema / $defs / FeatureVerticesToPointsInput / properties / in_features / description
      Added value: +"Absolute path to the existing input feature class, layer, or table. The path must be inside a configured PathGuard allowed root."
    • addedInput schema / $defs / FeatureVerticesToPointsInput / properties / out_features / description
      Added value: +"Absolute output dataset path to create. The path must be inside a configured PathGuard allowed root; existing outputs require overwrite=true."
    • addedInput schema / $defs / FeatureVerticesToPointsInput / properties / overwrite / description
      Added value: +"Set true only when replacing an existing output dataset is intended."
    • addedInput schema / $defs / FeatureVerticesToPointsInput / properties / point_location / description
      Added value: +"Which vertices to extract as points: ALL vertices, MID points, START vertices, END vertices, or BOTH_ENDS for line endpoints."
  2. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the burden of behavioral disclosure. It mentions using ArcPy and path constraints (in_features/out_features inside PathGuard allowed roots), but does not explain how the tool handles missing inputs, existing outputs (though the overwrite parameter exists), or other edge cases.

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 very concise, consisting of three sentences that front-load the core functionality and use cases without extraneous detail.

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

Completeness3/5

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

The description is fairly complete given the tool's simplicity and the detailed schema, but it does not explain the overwrite parameter or the point_location options' effects. Output schema is present but not described, which is acceptable.

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?

The input schema provides thorough descriptions for all parameters (in_features, out_features, overwrite, point_location), so the baseline is 3. The description adds little beyond the schema, only mentioning in_features and out_features by name without elaboration.

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 converts feature vertices to point features using ArcPy, specifies the types of vertices (endpoints, all vertices, midpoints, dangle points), and lists use cases (QA/QC, network checks, geometry inspection). This distinguishes it from sibling tools like feature_to_point.

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

Usage Guidelines3/5

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

The description provides context for when to use the tool (extracting vertices for QA/QC, network checks, etc.), but does not explicitly mention when not to use it or name alternative tools. The guidance is implied rather than explicit.

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