Skip to main content
Glama
Knight60

ArcGIS Pro MCP

by Knight60
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

set_layer_visibility

Toggle map layer visibility in ArcGIS Pro. Show or hide one layer, multiple layers, or all layers to control what appears on the map.

Instructions

Show or hide one layer, several layers, or every layer in the map.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
visibleYesTrue to show, False to hide.
map_nameNoMap to act on; defaults to the active map.
layer_nameNoSingle layer to change.
layer_namesNoSeveral layers to change.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv1.1.1
    • addedInput schema / properties / layer_name / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / layer_name / default
      Added value: +null
    • addedInput schema / properties / layer_name / description
      Added value: +"Single layer to change."
    • removedInput schema / properties / layer_name / type
      Removed value: -"string"
    • addedInput schema / properties / layer_names
      Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Several layers to change.",
+  "title": "Layer Names"
+}
    • addedInput schema / properties / map_name / description
      Added value: +"Map to act on; defaults to the active map."
    • addedInput schema / properties / visible / description
      Added value: +"True to show, False to hide."
    • changedInput schema / required
      Previous value: -[
-  "layer_name",
-  "visible"
-]New value: +[
+  "visible"
+]
  2. First observedv0.1.0

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. It doesn't disclose whether the operation is reversible, what happens if a layer is not found, whether it affects only the current view or persists in the project, or any rate limits. For a mutation tool, this is a significant gap.

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?

One sentence, front-loaded with the core action, and no wasted words. It efficiently conveys the scope of the tool.

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?

Given that there are no annotations and an output schema exists, the description is minimally adequate. It covers the basic action and scope, but lacks important behavioral context such as error handling, persistence, or side effects. For a 4-parameter mutation tool, more context would be beneficial.

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 coverage is 100%, so the schema already fully documents all parameters, including the visible flag and the distinction between layer_name and layer_names. The description adds little beyond reiterating that one, several, or all layers can be affected, which is already implied by the schema's parameters.

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 states a specific verb (show/hide) and resource (layers), clarifying that it works on one, several, or all layers. This distinguishes it from siblings like set_layer_transparency or set_layer_scale_range, but it doesn't explicitly name those alternatives.

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 guidance on when to use this tool versus alternatives, nor are prerequisites or conditions mentioned. The description only states what it does, not when it's appropriate.

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