Skip to main content
Glama
gaopengbin

cesium-mcp

by gaopengbin
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Hybrid

removeLayer

DestructiveIdempotent

Remove a specific managed layer from a CesiumJS 3D globe by its ID to clear cluttered scenes. Returns success status or error message.

Instructions

Remove a managed layer from the page. Returns { success: boolean, data?: unknown, message?: string, error?: string }.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesLayer ID to remove (get via listLayers)
sessionIdNoTarget browser session ID for multi-browser routing (optional)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNo
errorNo
messageNo
successYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changedv1.139.19
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "data": {},
+    "error": {
+      "type": "string"
+    },
+    "message": {
+      "type": "string"
+    },
+    "success": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "success"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changedv1.139.18
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  3. Changed2 schema fields changedv1.139.17
    • addedInput schema / properties / id / maxLength
      Added value: +200
    • addedInput schema / properties / id / minLength
      Added value: +1
  4. Changed2 schema fields changedv1.139.14
    • changedInput schema / properties / id / description
      Previous value: -"要移除的图层ID（可通过 listLayers 获取）"New value: +"Layer ID to remove (get via listLayers)"
    • addedInput schema / properties / sessionId
      Added value: +{
+  "description": "Target browser session ID for multi-browser routing (optional)",
+  "type": "string"
+}
  5. First observedv1.139.4

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already indicate destructiveHint=true and idempotentHint=true. The description adds useful context that the removal is scoped to the page's managed layer representation, but it does not elaborate on permanence or side effects on underlying data. No contradiction with annotations.

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 one short, front-loaded sentence followed by the return shape. Every word earns its place, and there is no redundancy or unnecessary detail.

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 simple two-parameter remove operation with good annotations and full schema coverage, the description is nearly sufficient. It could clarify what a 'managed layer' is or how it relates to listLayers, but those gaps are minor given the output schema and annotations.

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%, and both parameters already have clear descriptions in the schema. The tool description itself adds no parameter-level semantics, so the high schema coverage carries the weight.

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 uses a specific verb ('Remove') with a specific resource ('managed layer') and scope ('from the page'), which clearly distinguishes it from sibling tools like removeEntity and clearAll.

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?

No usage guidance is provided beyond the verb itself. The description does not mention when to use this tool versus removeEntity, clearAll, setLayerVisibility, or other layer-related tools, and no exclusions or alternatives are named.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/gaopengbin/cesium-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server