Skip to main content
Glama
652036

ArcGIS Pro MCP

by 652036

Zoom Active View To Layer

arcgis_pro_zoom_active_view_to_layer
Idempotent

Zoom the active ArcGIS Pro map view to a specified layer or its selection set in real time, keeping the current session focused on relevant features.

Instructions

实时将 ArcGIS Pro 当前地图视图缩放到指定图层或其选择集。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
aprx_pathYes
layer_nameYes
selection_onlyNo
symbolized_extentNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3/5.0
Behavior3/5

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

Annotations cover the safety profile (idempotentHint=true, destructiveHint=false, openWorldHint=false), and the description adds that the zoom is 'real-time' and can target a selection set. It still does not disclose which project/map the active view must belong to, whether an unsaved project is required, or other call-time constraints.

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 compact sentence that front-loads the action and target. Efficient, though it is perhaps too short for the tool's complexity.

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 described, but with four parameters at 0% coverage and heavy sibling overlap, the description leaves too much implicit. It is minimally viable rather than complete.

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%, so the description must carry parameter meaning, but it only gestures at selection_only ('或其选择集') and says nothing about aprx_path, layer_name, or symbolized_extent. The relationship between symbolized_extent and the described zoom behavior is left entirely unexplained.

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 states a specific verb (zoom) and resource (the active map view to a named layer or its selection set), which is clearer than a tautology. However, given siblings like arcgis_pro_zoom_to_layer, arcgis_pro_zoom_to_selection, and arcgis_pro_zoom_active_view_to_all_layers, it offers no explicit differentiation from those near-identical tools.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as zoom_to_layer or zoom_to_selection despite an extremely crowded sibling space. The user must infer when this tool is preferable over the other zoom tools.

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