cesium-mcp

zoomToExtent

Idempotent

Animate the camera to frame a geographic extent defined by west, south, east, and north coordinates in degrees. Accepts a bounding box and optional duration to control the view.

Instructions

Animate the camera to a west/south/east/north bounding box. Returns { success: boolean, data?: unknown, message?: string, error?: string }.

Input Schema

TableJSON Schema

Name	Required	Description
`bbox`	Yes	Geographic extent [west, south, east, north] in degrees
`duration`	No	Animation duration (seconds)
`sessionId`	No	Target browser session ID for multi-browser routing (optional)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	No
`error`	No
`message`	No
`success`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.139.19Aug 19, 2026

addedInput schema / properties / bbox / items
```
Added value: +{
+  "type": "number"
+}
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "data": {},
+    "error": {
+      "type": "string"
+    },
+    "message": {
+      "type": "string"
+    },
+    "success": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "success"
+  ],
+  "type": "object"
+}

Changed3 schema fields changedv1.139.18Aug 12, 2026

removedInput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

removedInput schema / properties / bbox / items

Removed value: -[
-  {
-    "maximum": 180,
-    "minimum": -180,
-    "type": "number"
-  },
-  {
-    "maximum": 90,
-    "minimum": -90,
-    "type": "number"
-  },
-  {
-    "maximum": 180,
-    "minimum": -180,
-    "type": "number"
-  },
-  {
-    "maximum": 90,
-    "minimum": -90,
-    "type": "number"
-  }
-]

addedInput schema / properties / bbox / prefixItems

Added value: +[
+  {
+    "maximum": 180,
+    "minimum": -180,
+    "type": "number"
+  },
+  {
+    "maximum": 90,
+    "minimum": -90,
+    "type": "number"
+  },
+  {
+    "maximum": 180,
+    "minimum": -180,
+    "type": "number"
+  },
+  {
+    "maximum": 90,
+    "minimum": -90,
+    "type": "number"
+  }
+]

Changed9 schema fields changedv1.139.17Jul 29, 2026

addedInput schema / properties / bbox

Added value: +{
+  "description": "Geographic extent [west, south, east, north] in degrees",
+  "items": [
+    {
+      "maximum": 180,
+      "minimum": -180,
+      "type": "number"
+    },
+    {
+      "maximum": 90,
+      "minimum": -90,
+      "type": "number"
+    },
+    {
+      "maximum": 180,
+      "minimum": -180,
+      "type": "number"
+    },
+    {
+      "maximum": 90,
+      "minimum": -90,
+      "type": "number"
+    }
+  ],
+  "maxItems": 4,
+  "minItems": 4,
+  "type": "array"
+}

changedInput schema / properties / duration / default
```
Previous value: -2New value: +1.5
```
addedInput schema / properties / duration / maximum
```
Added value: +60
```
addedInput schema / properties / duration / minimum
```
Added value: +0
```

removedInput schema / properties / east

Removed value: -{
-  "description": "East boundary longitude (degrees)",
-  "type": "number"
-}

removedInput schema / properties / north

Removed value: -{
-  "description": "North boundary latitude (degrees)",
-  "type": "number"
-}

removedInput schema / properties / south

Removed value: -{
-  "description": "South boundary latitude (degrees)",
-  "type": "number"
-}

removedInput schema / properties / west

Removed value: -{
-  "description": "West boundary longitude (degrees)",
-  "type": "number"
-}

changedInput schema / required

Previous value: -[
-  "west",
-  "south",
-  "east",
-  "north"
-]New value: +[
+  "bbox"
+]

Changed6 schema fields changedv1.139.14Apr 30, 2026

changedInput schema / properties / duration / description

Previous value: -"动画时长（秒）"New value: +"Animation duration (seconds)"

changedInput schema / properties / east / description

Previous value: -"东边界经度（度）"New value: +"East boundary longitude (degrees)"

changedInput schema / properties / north / description

Previous value: -"北边界纬度（度）"New value: +"North boundary latitude (degrees)"

addedInput schema / properties / sessionId

Added value: +{
+  "description": "Target browser session ID for multi-browser routing (optional)",
+  "type": "string"
+}

changedInput schema / properties / south / description

Previous value: -"南边界纬度（度）"New value: +"South boundary latitude (degrees)"

changedInput schema / properties / west / description

Previous value: -"西边界经度（度）"New value: +"West boundary longitude (degrees)"

First observedv1.139.4Mar 15, 2026

TDQS

A3.6/5.0

Behavior3/5

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

The annotations already indicate idempotentHint true and destructiveHint false, so the description does not contradict these. However, the description adds little beyond stating the animation action; it does not mention potential side effects, permissions, or behavior on invalid input. Given annotations cover the main safety aspects, a baseline score of 3 is appropriate.

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, concise sentence that conveys the essential purpose without any fluff. It efficiently states the action and target, making it easy to understand at a glance.

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 that the schema fully documents parameters and annotations cover safety, the description is adequately complete for a tool of this simplicity. It clearly states the action and return type, though it omits usage guidance, which is a minor gap. Overall, the description is complete enough for an agent to understand the tool's function.

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?

The schema provides detailed descriptions for all parameters (bbox, duration, sessionId) with types, ranges, and defaults. The description adds no extra clarity about parameters, and since schema coverage is 100%, a baseline score of 3 is justified.

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 action ('Animate the camera') and the target ('a west/south/east/north bounding box'), making it obvious what the tool does. It distinguishes from sibling tools by specifying animation, which is a key differentiator from setView or flyTo that might be immediate.

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?

The description does not provide any context on when to use this tool versus alternatives like flyTo or setView. It lacks guidance on conditions or scenarios where this tool is preferred, which is important given the presence of similar camera-control tools in the sibling list.

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