Skip to main content
Glama
muend

arcgis-mcp-bridge

by muend
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

smooth_features

Smooths polygon or polyline geometries by applying ArcPy smoothing algorithms, producing a generalized output feature class without altering the original data.

Instructions

Smooth polygon or polyline geometry using ArcPy SmoothPolygon or SmoothLine after detecting the input shape type. Use this for cartographic cleanup where angular boundaries or lines need a more generalized appearance. Writes a new smoothed output feature class without modifying the source dataset.

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 changedv1.0.1
    • addedInput schema / $defs / SmoothFeaturesInput / description
      Added value: +"Input contract for smoothing polygon or polyline geometry."
    • addedInput schema / $defs / SmoothFeaturesInput / properties / algorithm / description
      Added value: +"Smoothing algorithm passed to ArcPy. PAEK uses a tolerance distance; BEZIER_INTERPOLATION creates smoother curves without a tolerance in some ArcPy workflows."
    • addedInput schema / $defs / SmoothFeaturesInput / 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 / SmoothFeaturesInput / 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 / SmoothFeaturesInput / properties / overwrite / description
      Added value: +"Set true only when replacing an existing output dataset is intended."
    • changedInput schema / $defs / SmoothFeaturesInput / properties / tolerance / description
      Previous value: -"PAEK smoothing tolerance, e.g. '100 Meters'"New value: +"PAEK smoothing tolerance with units, for example '100 Meters'. Required by the current worker implementation."
  2. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations provided, the description carries full burden. It discloses that the tool detects input shape type, writes a new output without modifying source, and uses ArcPy functions. It lacks details on performance, handling of invalid geometries, or constraints like tolerance being required only for PAEK.

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 concise with three sentences, no fluff, and front-loads the key verb and resource. Every sentence contributes meaningful information.

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 covers the main action and outcome but omits details about parameters (algorithm, tolerance, overwrite) and output schema behavior. Given the existence of an output schema, the lack of output description is acceptable, but the parameter omissions reduce completeness.

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

Parameters2/5

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

Schema description coverage is 0% per context, meaning the description adds no parameter-specific info. Although the schema itself has descriptions for all five fields, the description does not compensate for the low coverage. It could mention tolerance or algorithm, but it does not.

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

Purpose4/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: smoothing polygon or polyline geometry using ArcPy functions. It specifies the method (SmoothPolygon/SmoothLine) and outcome (new feature class). While it doesn't explicitly name sibling tools like simplify_features, the mention of 'cartographic cleanup' and 'more generalized appearance' provides differentiation.

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 advises use for cartographic cleanup of angular boundaries or lines, giving a clear scenario. However, it does not specify when not to use this tool or mention alternatives, leaving room for ambiguity in selection among sibling tools like simplify_features.

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