Skip to main content
Glama
Knight60

ArcGIS Pro MCP

by Knight60
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

zoom_to_layer

Zoom the ArcGIS Pro map view to a layer or table's full extent, with optional padding, to quickly focus on your target data.

Instructions

Zoom the map view to a layer's extent.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
map_nameNoMap to act on; defaults to the active map.
layer_nameYesLayer or table name as shown by get_layers, or a full dataset path.
expand_factorNoOptional padding, e.g. 0.1 for 10% extra around the extent.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.1.1
    • addedInput schema / properties / expand_factor
      Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Optional padding, e.g. 0.1 for 10% extra around the extent.",
+  "title": "Expand Factor"
+}
    • addedInput schema / properties / layer_name / description
      Added value: +"Layer or table name as shown by get_layers, or a full dataset path."
    • addedInput schema / properties / map_name / description
      Added value: +"Map to act on; defaults to the active map."
  2. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description needs to carry more behavioral load. It implies a view-only mutation but doesn't state whether a layer must be visible, whether it errors on missing layers, or whether it changes the active map. It also doesn't disclose whether the zoom is animated or immediate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single, front-loaded sentence with zero waste. It could be improved by including one sentence about when to use it versus related view tools, but the structure is tight.

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?

An output schema exists, so return values need not be explained. However, for a view-mutating tool with no annotations and several sibling tools that also affect the view, the description omits when it must be used instead of alternatives or whether a layer must be selected/visible first.

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 coverage is 100%, so map_name, layer_name, and expand_factor are already fully documented in the schema. The description adds no parameter syntax or format details beyond what the schema provides, making the baseline 3 appropriate.

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?

States a specific verb (zoom) and resource (map view to a layer's extent), clearly distinguishing it from siblings like zoom_to_selection. The purpose is clear without requiring schema inspection, though it doesn't explicitly call out the sibling it differs from.

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?

No explicit when/when-not guidance. An agent can infer it should be used when it wants to navigate the view to a layer, but the description doesn't contrast it with zoom_to_selection, apply_bookmark, or set_map_view, which are all competing ways to change the view.

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