Skip to main content
Glama
muend

arcgis-mcp-bridge

by muend
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

simplify_features

Simplify polygon or polyline geometry by reducing vertex density. Use for cartography, web export, or scale-appropriate analysis without altering source data.

Instructions

Simplify polygon or polyline geometry using ArcPy SimplifyPolygon or SimplifyLine after detecting the input shape type. Use this to reduce vertex density for cartography, web export, performance, or scale-appropriate analysis. Writes a simplified output feature class and does not mutate the source 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 changedv1.0.1
    • addedInput schema / $defs / SimplifyFeaturesInput / description
      Added value: +"Input contract for simplifying polygon or polyline geometry."
    • addedInput schema / $defs / SimplifyFeaturesInput / properties / algorithm / description
      Added value: +"Simplification algorithm passed to ArcPy. POINT_REMOVE is general purpose, BEND_SIMPLIFY preserves major bends, and WEIGHTED_AREA is commonly used for polygon simplification."
    • addedInput schema / $defs / SimplifyFeaturesInput / 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 / SimplifyFeaturesInput / 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 / SimplifyFeaturesInput / properties / overwrite / description
      Added value: +"Set true only when replacing an existing output dataset is intended."
    • changedInput schema / $defs / SimplifyFeaturesInput / properties / tolerance / description
      Previous value: -"e.g. '10 Meters'"New value: +"Simplification tolerance with units, for example '10 Meters'. Larger values remove more detail."
  2. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the burden. It states the tool writes an output feature class and does not mutate source features, and automatically detects shape type to choose between SimplifyPolygon and SimplifyLine. This adds meaningful behavioral context beyond the schema.

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: first for core purpose, second for use cases, third for behavioral note. No wasted words, well-front-loaded.

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 complexity, the description adequately covers purpose, usage scenarios, and non-destructive nature. With an output schema present, return values need not be explained. Missing are error handling and prerequisites like ArcPy license, but overall complete for typical use.

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 tool description does not elaborate on parameters; however, the input schema includes detailed descriptions for each property (e.g., algorithm enum, tolerance units). Since the schema provides adequate parameter semantics, the description adds no additional value, warranting a baseline score of 3.

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 simplifies polygon or polyline geometry using specific ArcPy functions and detects shape type automatically. It specifies the resource (geometry) and verb (Simplify), and distinguishes from smooth_features by focusing on vertex density reduction.

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 provides explicit use cases: cartography, web export, performance, scale-appropriate analysis. However, it does not mention when not to use it or alternative tools like smooth_features, missing some context for tool selection.

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