Skip to main content
Glama
muend

arcgis-mcp-bridge

by muend
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

add_layer_to_map

Add a GIS dataset (feature class, raster, table) as a layer to a specific map within an ArcGIS Pro .aprx project. Supports saving the project after addition.

Instructions

Add a dataset to a map inside a saved ArcGIS Pro .aprx project using arcpy.mp addDataFromPath. Use this to load feature classes, rasters, tables, or other supported GIS datasets into an existing project map before styling, exporting, or layout automation. Operates on the saved .aprx file, not a live ArcGIS Pro session, and saves the project when save=true.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.6.3
    • addedInput schema / $defs / AddLayerToMapInput / description
      Added value: +"Input contract for adding a dataset as a layer to a project map."
    • changedInput schema / $defs / AddLayerToMapInput / properties / aprx_path / description
      Previous value: -"Absolute .aprx path."New value: +"Absolute path to the saved ArcGIS Pro .aprx project file. The path must be inside a configured PathGuard allowed root. Tools operate on the saved project file, not a live open ArcGIS Pro session."
    • changedInput schema / $defs / AddLayerToMapInput / properties / data_path / description
      Previous value: -"Dataset to add (FC/raster path)."New value: +"Absolute path to the feature class, table, raster, or supported GIS dataset to add as a map layer. The dataset must be inside a configured PathGuard allowed root."
    • changedInput schema / $defs / AddLayerToMapInput / properties / map_name / description
      Previous value: -"Map name; None targets the first map."New value: +"Name of the map inside the .aprx project. Use None to target the first map returned by ArcGIS Pro."
    • changedInput schema / $defs / AddLayerToMapInput / properties / save / description
      Previous value: -"Persist the .aprx afterwards."New value: +"When true, save the .aprx project after adding the layer. Use false for temporary in-memory inspection before another operation."
  2. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses key behaviors: operates on saved .aprx files (not live sessions), saves when save=true, and uses arcpy.mp addDataFromPath. It does not mention error conditions or permissions, but the core safety profile (non-destructive addition) is evident.

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?

Three tightly written sentences deliver purpose, usage context, and behavioral note without extraneous words. Every sentence earns its place, making it efficient for an AI agent to parse.

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 presence of a comprehensive schema and an output schema (not shown), the description provides enough context: operation, data types, saved-file constraint, and save behavior. It could mention default map_name behavior or potential errors, but overall it is largely complete for a tool of this complexity.

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 descriptions cover all four parameters with sufficient detail, so the baseline is 3. The tool description does not add additional semantic information about parameters beyond what the schema already provides, meeting the minimum but not exceeding.

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 verb 'Add', the resource 'dataset to a map inside an .aprx project', and provides examples of supported data types. It distinguishes from live sessions and mentions the underlying arcpy method, leaving no ambiguity about the tool's function.

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?

The description gives context for when to use the tool ('before styling, exporting, or layout automation') and mentions it operates on saved files, implying it's for batch/automation workflows. It does not explicitly contrast with sibling tools like remove_layer_from_map, but the unique operation (adding) is clear.

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