Skip to main content
Glama
Knight60

ArcGIS Pro MCP

by Knight60
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

get_layers

List all layers, draw order, group nesting, and standalone tables in an ArcGIS Pro map to inspect project contents before editing or querying.

Instructions

List the layers (with draw order and group nesting) and standalone tables in a map. Start here to see what is in the project.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
map_nameNoMap to act on; defaults to the active map.
include_basemapNoInclude basemap layers.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.1.1
    • addedInput schema / properties / include_basemap
      Added value: +{
+  "default": false,
+  "description": "Include basemap layers.",
+  "title": "Include Basemap",
+  "type": "boolean"
+}
    • addedInput schema / properties / map_name / description
      Added value: +"Map to act on; defaults to the active map."
  2. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses the shape of the result (draw order, group nesting, standalone tables) but says nothing about scope limits, whether basemap layers are excluded by default, or pagination/size behavior for large maps.

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 with zero filler; the substantive content (draw order, group nesting, standalone tables) is front-loaded and the usage hint follows it.

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?

An output schema exists, so return values need not be explained, and the description sketches what the listing contains. For a safe read-only inventory tool with a fully documented schema, this is close to complete; only the basemap default behavior and result size are unaddressed.

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%, so both parameters (map_name with active-map default, include_basemap default false) are already fully documented in the schema. The description adds no meaning beyond that, so the baseline 3 applies.

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?

States a specific verb and resource ('List the layers ... and standalone tables in a map') and even names the contents of the result (draw order, group nesting). An agent can distinguish this from sibling list_maps and get_layer_info without opening a schema.

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

Usage Guidelines4/5

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

'Start here to see what is in the project' gives clear entry-point guidance, telling the agent when this tool is the right first call. It stops short of naming alternatives or exclusions (e.g., use get_layer_info for one layer's details), so it is not a full 5.

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