ArcGIS Pro MCP

Overview Schema Source Related Servers Discussions Admin

set_layer_renderer

Sets a layer's symbology in ArcGIS Pro: choose a single symbol, unique values by category, or a graduated colour or size scheme driven by a numeric field.

Instructions

Change a layer's symbology: a single symbol, unique values by category, or a classified/continuous colour scheme by numeric field.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`color`	No	Fill colour for simple symbology as [r, g, b] or [r, g, b, alpha].
`field`	No	Field to symbolise by (all types except simple).
`label`	No	Legend label for simple symbology.
`fields`	No	Several fields for unique_values symbology.
`map_name`	No	Map to act on; defaults to the active map.
`color_ramp`	No	Colour ramp name, e.g. "Viridis" -- see list_color_ramps.
`layer_name`	Yes	Layer or table name as shown by get_layers, or a full dataset path.
`break_count`	No	Number of classes for graduated symbology.
`symbol_size`	No	Point/line symbol size in points.
`class_colors`	No	Explicit colour per class for graduated symbology, lowest class first, e.g. [[244,166,166],[249,220,164],[147,203,163]]. Use it when no built-in ramp has the colours you want.
`transparency`	No	Layer transparency 0-100.
`value_colors`	No	Explicit colours per category for unique_values, e.g. {"Forest": [34, 139, 34]}.
`outline_color`	No	Outline colour as [r, g, b].
`outline_width`	No	Outline width in points.
`renderer_type`	No	simple, unique_values, graduated_colors, graduated_symbols or unclassed_colors.	simple
`max_symbol_size`	No	Largest size for graduated_symbols.
`min_symbol_size`	No	Smallest size for graduated_symbols.
`classification_method`	No	NaturalBreaks, EqualInterval, Quantile, StandardDeviation, GeometricInterval or DefinedInterval.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed18 schema fields changedv1.1.1Sep 13, 2026

addedInput schema / properties / break_count / description

Added value: +"Number of classes for graduated symbology."

addedInput schema / properties / class_colors

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Explicit colour per class for graduated symbology, lowest class first, e.g. [[244,166,166],[249,220,164],[147,203,163]]. Use it when no built-in ramp has the colours you want.",
+  "title": "Class Colors"
+}

addedInput schema / properties / classification_method

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "NaturalBreaks, EqualInterval, Quantile, StandardDeviation, GeometricInterval or DefinedInterval.",
+  "title": "Classification Method"
+}

addedInput schema / properties / color / description

Added value: +"Fill colour for simple symbology as [r, g, b] or [r, g, b, alpha]."

addedInput schema / properties / color_ramp / description

Added value: +"Colour ramp name, e.g. \"Viridis\" -- see list_color_ramps."

addedInput schema / properties / field / description

Added value: +"Field to symbolise by (all types except simple)."

addedInput schema / properties / fields

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Several fields for unique_values symbology.",
+  "title": "Fields"
+}

addedInput schema / properties / label

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Legend label for simple symbology.",
+  "title": "Label"
+}

addedInput schema / properties / layer_name / description

Added value: +"Layer or table name as shown by get_layers, or a full dataset path."

addedInput schema / properties / map_name / description

Added value: +"Map to act on; defaults to the active map."

addedInput schema / properties / max_symbol_size

Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Largest size for graduated_symbols.",
+  "title": "Max Symbol Size"
+}

addedInput schema / properties / min_symbol_size

Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Smallest size for graduated_symbols.",
+  "title": "Min Symbol Size"
+}

addedInput schema / properties / outline_color / description
```
Added value: +"Outline colour as [r, g, b]."
```

addedInput schema / properties / outline_width

Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Outline width in points.",
+  "title": "Outline Width"
+}

addedInput schema / properties / renderer_type / description

Added value: +"simple, unique_values, graduated_colors, graduated_symbols or unclassed_colors."

addedInput schema / properties / symbol_size

Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Point/line symbol size in points.",
+  "title": "Symbol Size"
+}

addedInput schema / properties / transparency

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Layer transparency 0-100.",
+  "title": "Transparency"
+}

addedInput schema / properties / value_colors

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Explicit colours per category for unique_values, e.g. {\"Forest\": [34, 139, 34]}.",
+  "title": "Value Colors"
+}

First observedv0.1.0Jul 7, 2026

TDQS

B3.1/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 of behavioral disclosure. It states that the operation changes symbology, but it does not disclose mutation side effects such as persistence, permissions, reversibility, or whether changes require saving the project.

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?

The description is a single front-loaded sentence with no wasted words. It states the core operation and the supported symbology concepts efficiently, leaving detail to the rich schema.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The input schema is highly detailed and an output schema exists, so return values need not be explained. However, for a complex 18-parameter mutation tool with no annotations, the description is minimally complete and omits usage context and behavioral caveats.

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 the schema already documents all 18 parameters thoroughly. The description adds only a high-level mapping to renderer modes and does not add syntax, defaults, or parameter interaction details beyond the schema.

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?

The description gives a specific verb and resource: 'Change a layer's symbology,' and it enumerates three broad modes (single symbol, unique values, classified/continuous colour scheme). It distinguishes the operation from read-only or apply-from-layer siblings by scope, though it does not name alternatives explicitly.

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?

There is no explicit guidance about when to use this tool versus siblings like get_layer_symbology, apply_symbology_from_layer, set_raster_symbology, or set_layer_transparency. Usage is only implied by the verb 'Change,' leaving the agent to infer prerequisites and selection criteria.

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

Deploy Server