Skip to main content
Glama
muend

arcgis-mcp-bridge

execute_spatial_tool

Execute buffer and clip analysis on GIS datasets by specifying input features, tool parameters, and output path.

Instructions

Execute one allowlisted geoprocessing tool (Buffer_analysis, Clip_analysis).

Args:
    tool: Allowlisted tool name, e.g. 'Buffer_analysis'.
    in_features: Absolute path to the source dataset (inside allowed roots).
    parameters: Tool-specific arguments. Buffer requires
        'buffer_distance_or_field' (e.g. '100 Meters'); Clip requires
        'clip_features' (a dataset path).
    out_features: Output path. Omit to auto-name inside the scratch GDB.
    overwrite: Must be true to replace an existing output (explicit opt-in).

Returns:
    ExecuteSpatialToolOutput as JSON: status, output_path, messages,
    elapsed_seconds.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toolYes
overwriteNo
parametersYes
in_featuresYes
out_featuresNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

No annotations are provided, so the description must disclose behavioral traits. It mentions that overwrite must be true to replace an existing output, indicating explicit opt-in. It also describes the return format. However, it does not clarify whether input data is modified (likely not, but not stated) or detail error behavior for invalid tool names. The description adds useful context but could be more comprehensive.

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 and well-structured: a brief opening sentence, followed by a bullet-like list of parameters. Every sentence adds value without redundancy. The key information is 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 (5 parameters, nested object, no annotations), the description covers the essential aspects: allowed tools, parameter meanings, overwrite behavior, and return format. It mentions allowed roots and scratch GDB for context. However, it could include more on error cases or the validation of tool names. The presence of an output schema partially compensates for missing return details.

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

Parameters5/5

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

The input schema has 0% description coverage, so the description must compensate. It explains each parameter: tool as allowlisted name, in_features as absolute path, parameters with tool-specific examples, out_features as optional auto-naming, and overwrite as explicit opt-in. This adds significant meaning beyond the schema.

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 executes an allowlisted geoprocessing tool, with specific examples (Buffer_analysis, Clip_analysis). This distinguishes it from sibling tools which are individual geoprocessing tools, making the purpose and scope immediately clear.

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 implies that this tool is for running specific tools not individually exposed, and lists which tools are allowed. However, it does not explicitly state when to use this tool versus the dedicated sibling tools, nor does it provide guidance on when not to use it. The examples provide some context, but explicit alternatives or exclusions would improve clarity.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/muend/arcgis-mcp-bridge'

If you have feedback or need assistance with the MCP directory API, please join our Discord server