ArcGIS Pro MCP

Overview Schema Source Related Servers Discussions Admin

list_geoprocessing_tools

Search available geoprocessing tools by name, wildcard, or toolbox to find the right arcpy function for your ArcGIS Pro task.

Instructions

Search the available geoprocessing tools by name.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Maximum tool names to return.
`toolbox`	No	Restrict to one toolbox alias, e.g. "analysis" or "management".
`wildcard`	No	Name pattern, e.g. "Buffer".	*

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv1.1.1Sep 13, 2026

addedInput schema / properties / limit

Added value: +{
+  "default": 500,
+  "description": "Maximum tool names to return.",
+  "title": "Limit",
+  "type": "integer"
+}

addedInput schema / properties / toolbox

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Restrict to one toolbox alias, e.g. \"analysis\" or \"management\".",
+  "title": "Toolbox"
+}

addedInput schema / properties / wildcard / description
```
Added value: +"Name pattern, e.g. \"*Buffer*\"."
```

First observedv0.1.0Jul 7, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations at all, the description carries the full burden, and it discloses only that matching is by name. Read-only intent is inferable from 'Search', but pagination/limit behavior and the fact that it returns names only (not full tool definitions) are not stated; an output schema covers returns, which lightens the gap.

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?

One sentence, front-loaded with the verb and resource, zero filler. Nothing could be removed without losing meaning.

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

Completeness5/5

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

For a zero-required-parameter search call with fully documented parameters and an output schema, this is complete enough to invoke correctly; the missing sibling routing is a discoverability nit rather than a blocker.

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 description coverage is 100% — limit, toolbox alias and wildcard pattern are each documented in the schema with examples. The description's 'by name' adds a mild hint about the wildcard parameter but no syntax or default information, so baseline 3 applies.

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?

Specific verb ('Search'), specific resource ('geoprocessing tools') and a stated search axis ('by name'). It is distinguishable from run_geoprocessing_tool and describe_geoprocessing_tool by implication, but it never explicitly contrasts itself with those siblings.

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

Usage Guidelines2/5

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

No when-to-use guidance, no prerequisites, and no mention of alternatives. The agent must infer that this is a discovery step preceding describe_geoprocessing_tool or run_geoprocessing_tool; nothing in the text says so.

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

Deploy Server