Skip to main content
Glama
Knight60

ArcGIS Pro MCP

by Knight60
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

create_map

Create a new map or scene in the ArcGIS Pro project, specifying a name and optional coordinate system or basemap. Adds a fresh map to your session for further layer and geoprocessing work.

Instructions

Create a new map or scene in the project.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
epsgNoOptional coordinate system WKID, e.g. 32647.
nameYesName for the new map.
basemapNoOptional basemap to add, e.g. 'Topographic'.
map_typeNoMAP or SCENE.MAP

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.1.1
    • addedInput schema / properties / basemap
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Optional basemap to add, e.g. 'Topographic'.",
+  "title": "Basemap"
+}
    • addedInput schema / properties / epsg
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Optional coordinate system WKID, e.g. 32647.",
+  "title": "Epsg"
+}
    • addedInput schema / properties / map_type / description
      Added value: +"MAP or SCENE."
    • addedInput schema / properties / name / description
      Added value: +"Name for the new map."
  2. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states the tool creates a map, but says nothing about permissions, whether the new map becomes the active map, whether the change persists only after save_project, or any error conditions. For a mutation tool with zero annotation coverage, this is a substantial gap.

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 wasted-free sentence with the key action front-loaded. It is arguably too terse for a mutation tool, but there is no padding or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/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, but the absence of annotations and any behavioral/prerequisite context leaves a mutation tool under-specified for an agent deciding whether and how to call it.

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 epsg, basemap, name, and map_type are already documented in the schema with examples. The description only echoes map/scene, which corresponds to map_type, adding little beyond the schema. Baseline 3 applies.

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?

"Create a new map or scene in the project" gives a specific verb (create) and resource (map/scene), and the mention of both map and scene maps to the map_type parameter. It is clearly distinguishable from siblings like list_maps or remove_map, though it does not explicitly name them.

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 guidance on when to use this versus alternatives, nor any prerequisites (e.g. project open, whether the map becomes active, whether it must be created before add_layer). The agent must infer usage entirely.

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