ShowMeOnMap

Set the map camera (direct)

set_camera

Idempotent

Override the workspace camera. Latest set_camera op wins during replay. Two modes: fitBounds with a [w,s,e,n] bbox (plus optional padding/animateMs), or flyTo with [lng,lat] center + zoom (plus optional pitch/bearing/animateMs). Covers requests like "zoom to Japan", "center on Paris at z=10", or framing a filtered layer. Equivalent to the camera move mutate_map would emit, but skips the NL roundtrip.

Input Schema

TableJSON Schema

Name	Required	Description
`camera`	Yes
`map_id`	Yes
`rationale`	No	Optional short label (≤300 chars) for the map edit history, e.g. "add wildfire layer". Omit it to send nothing beyond the tool arguments.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 29, 2026

changedInput schema / properties / rationale / description

Previous value: -"Short audit-log label (≤300 chars) stating the user-facing goal this call serves, e.g. \"add wildfire layer for the user's California query\". Required on every call. Stored in the operations log so map edits stay traceable — we never see your chat history."New value: +"Optional short label (≤300 chars) for the map edit history, e.g. \"add wildfire layer\". Omit it to send nothing beyond the tool arguments."

changedInput schema / required

Previous value: -[
-  "map_id",
-  "camera",
-  "rationale"
-]New value: +[
+  "map_id",
+  "camera"
+]

Changed1 schema field changedSep 29, 2026

changedInput schema / properties / camera / oneOf

Previous value: -[
-  {
-    "properties": {
-      "animateMs": {
-        "description": "Animation duration in ms. 0 = instant jump.",
-        "minimum": 0,
-        "type": "number"
-      },
-      "bounds": {
-        "description": "[west, south, east, north] bbox in WGS84 degrees.",
-        "items": [
-          {
-            "type": "number"
-          },
-          {
-            "type": "number"
-          },
-          {
-            "type": "number"
-          },
-          {
-            "type": "number"
-          }
-        ],
-        "type": "array"
-      },
-      "mode": {
-        "const": "fitBounds",
-        "type": "string"
-      },
-      "padding": {
-        "description": "Pixel padding around the bbox. Default is the renderer default.",
-        "minimum": 0,
-        "type": "number"
-      }
-    },
-    "required": [
-      "mode",
-      "bounds"
-    ],
-    "type": "object"
-  },
-  {
-    "properties": {
-      "animateMs": {
-        "description": "Animation duration in ms. 0 = instant jump.",
-        "minimum": 0,
-        "type": "number"
-      },
-      "bearing": {
-        "description": "Rotation in degrees, 0-360.",
-        "type": "number"
-      },
-      "center": {
-        "description": "[lng, lat] in WGS84.",
-        "items": [
-          {
-            "type": "number"
-          },
-          {
-            "type": "number"
-          }
-        ],
-        "type": "array"
-      },
-      "mode": {
-        "const": "flyTo",
-        "type": "string"
-      },
-      "pitch": {
-        "description": "Tilt in degrees, 0-60.",
-        "type": "number"
-      },
-      "zoom": {
-        "type": "number"
-      }
-    },
-    "required": [
-      "mode",
-      "center",
-      "zoom"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "properties": {
+      "animateMs": {
+        "description": "Animation duration in ms. 0 = instant jump.",
+        "minimum": 0,
+        "type": "number"
+      },
+      "bounds": {
+        "description": "[west, south, east, north] bbox in WGS84 degrees.",
+        "items": {
+          "type": "number"
+        },
+        "maxItems": 4,
+        "minItems": 4,
+        "type": "array"
+      },
+      "mode": {
+        "const": "fitBounds",
+        "type": "string"
+      },
+      "padding": {
+        "description": "Pixel padding around the bbox. Default is the renderer default.",
+        "minimum": 0,
+        "type": "number"
+      }
+    },
+    "required": [
+      "mode",
+      "bounds"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "animateMs": {
+        "description": "Animation duration in ms. 0 = instant jump.",
+        "minimum": 0,
+        "type": "number"
+      },
+      "bearing": {
+        "description": "Rotation in degrees, 0-360.",
+        "type": "number"
+      },
+      "center": {
+        "description": "[lng, lat] in WGS84.",
+        "items": {
+          "type": "number"
+        },
+        "maxItems": 2,
+        "minItems": 2,
+        "type": "array"
+      },
+      "mode": {
+        "const": "flyTo",
+        "type": "string"
+      },
+      "pitch": {
+        "description": "Tilt in degrees, 0-60.",
+        "type": "number"
+      },
+      "zoom": {
+        "type": "number"
+      }
+    },
+    "required": [
+      "mode",
+      "center",
+      "zoom"
+    ],
+    "type": "object"
+  }
+]

First observedJul 19, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Adds behavior beyond annotations: it discloses the override semantics and replay determinism ("Latest set_camera op wins during replay"), which matters for an idempotentHint=true, destructiveHint=false mutation. It does not describe the response or failure behavior, but for an idempotent camera op the disclosed constraints are the meaningful ones.

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?

Three sentences, all front-loaded with the core purpose first, then modes, then the mutate_map relationship. Dense but every clause carries distinct information; only the trailing "Covers requests like..." sentence is mildly redundant with the mode enumeration.

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?

For a 3-param mutation with no output schema, the description supplies the mode structure, override/replay semantics, and the sibling relationship. An agent can invoke it correctly. The missing piece is any mention of the rationale field's map-edit-history role.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With only 33% schema coverage, the description compensates well by spelling out each mode's fields: fitBounds takes [w,s,e,n] bbox plus optional padding/animateMs; flyTo takes [lng,lat] center + zoom plus optional pitch/bearing/animateMs. It does not explain the rationale parameter's history-log purpose, but it covers the two hard-to-infer discriminated branches.

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?

Opens with a specific verb+resource ("Override the workspace camera") and immediately enumerates the two supported modes, so an agent knows exactly what the tool does. It also names the sibling it makes redundant (mutate_map's camera move), which is rare and valuable differentiation.

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?

Explicitly states the direct-usage case and the alternative: "Equivalent to the camera move mutate_map would emit, but skips the NL roundtrip," plus concrete request examples ("zoom to Japan", "center on Paris at z=10"). It stops short of stating when a direct camera set is inappropriate (e.g. when a full NL edit is wanted), but the routing context is clear.

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

All ShowMeOnMap tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?