Skip to main content
Glama
Sign In
arcpro-mcp

arcpro-mcp

by qiobn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Zoom to Layer

zoom_to_layer
Idempotent

Zoom the active map to the full extent of a specified layer, making the layer fully visible in the map view.

Instructions

Zoom the active map view to a layer's full extent. Requires an open map view.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "layer": "<layer>"
    },
    "name": "zoom_to_layer"
  }
}

Input Schema

NameRequiredDescriptionDefault
layerYes
map_nameNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the idempotentHint annotation, description adds concrete behavior details (zooms to full extent) and clarifies the need for an open map view, enhancing understanding of the tool's action.

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?

Two short sentences, front-loads the main action, and every word adds value with no redundancy.

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?

For a simple zoom tool with an output schema and minimal parameters, the description covers the key behavioral context and prerequisites, though it could benefit from parameter examples or further usage hints.

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?

With 0% schema description coverage, the description does not explain what the 'layer' and 'map_name' parameters represent or their relationship, leaving significant ambiguity for an AI agent.

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?

Specifies verb 'zoom' and resource 'layer' with qualifiers 'active map view' and 'full extent', clearly distinguishing from sibling tools that perform different operations on map layers.

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?

States prerequisite 'Requires an open map view', providing clear context, but offers no guidance on when to use this tool instead of alternatives or when not to use it.

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