arcpro-mcp

by qiobn

Overview Schema Source Related Servers Discussions Admin

Python

Local

List Layers

list_layers

Read-only

List layers in the active or specified map, returning their name, visibility, and type (feature, raster, group).

Instructions

List layers in the active map (or a named map). Returns each layer's name, visibility, and whether it is a feature/raster/group layer.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_layers"
  }
}

Input Schema

Name	Required	Description	Default
`map_name`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 14, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true. The description adds behavioral detail about the return value (name, visibility, layer type), which is helpful. It does not contradict annotations.

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?

One concise sentence covering purpose and return structure. Very efficient, though slightly more structure (e.g., bullet list) could improve readability.

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 simplicity, readOnlyHint annotation, and existing output schema, the description adequately covers return contents and usage context. It could mention that it lists all layers without filtering, but overall sufficient.

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

Parameters4/5

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

The description clarifies the single parameter map_name by explaining that an empty value corresponds to the active map, while a named map is used otherwise. This adds meaning beyond the schema's simple 'Map Name' string and default=''.

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 lists layers in the active or named map, specifying the returned attributes (name, visibility, type). This distinguishes it from sibling tools like add_raster_layer or remove_layer.

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 explicit guidance is given on when to use this tool versus alternatives. The description only says what it does, not when it is appropriate or when to use other list tools like list_fields or list_feature_classes.

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