Skip to main content
Glama

Does this MapLibre / CesiumJS feature work on Ortho Earth?

check_compat
Read-onlyIdempotent

Looks up how the official MapLibre GL JS examples and CesiumJS Sandcastle examples matching the query run on Ortho Earth (same picture / same answers / runs partly / does not run), with notes and links to side-by-side comparisons, and how MapLibre style properties are read (e.g. "fill-extrusion", "line-dasharray").

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "check_compat"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesFeature or example name, e.g. "terrain", "popup", "3d tiles", "fill-pattern"
libraryNoall

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, and the description is consistent with a fixed-corpus read lookup. It adds useful output framing (same picture / same answers / runs partly / does not run, plus notes and side-by-side links) but says nothing about behavior when no example matches or how fuzzy matching works.

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?

A single front-loaded sentence that leads with the verb and resource, then stacks return categories and example inputs. Dense but every clause carries information; minor cost is the nested parenthetical and example list that makes it a long read.

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?

There is no output schema, and the description compensates by naming the four result categories and the accompanying notes and comparison links. Gaps remain around the 'library' parameter and no-match behavior, but for a two-parameter read-only lookup this is close to complete.

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?

With 50% schema description coverage, the undocumented 'library' parameter is never mentioned, and only its enum values and default make it usable. The description does add value for 'query' by naming valid inputs such as 'fill-extrusion' and 'line-dasharray', going beyond the schema's terse example string.

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?

States a specific verb and resource: it looks up how official MapLibre GL JS and CesiumJS Sandcastle examples matching a query run on Ortho Earth, and it enumerates the four compatibility outcomes. That is clearly distinct from generic doc/search siblings, though it never names an alternative tool to route to.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by 'matching the query' and by the example values ('terrain', 'popup'), so an agent can infer this is the compatibility-check tool. There is no explicit when-to-use/when-not guidance and no pointer to search_docs or lookup_api for related questions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.