Skip to main content
Glama

Search the Ortho Earth documentation

search_docs
Read-onlyIdempotent

Full-text search over the Ortho Earth documentation (the recipe, the changelog, migration guides from MapLibre GL JS, CesiumJS, Leaflet and Google Maps, the engine overview, GeoPBF, Gint, comparison articles). Returns the best matching sections with their source page.

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": "search_docs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesWords to look for, e.g. "3D Tiles", "terrain exaggeration", "popup"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuine behavioral context beyond that: it names the indexed corpus and states the return shape (ranked sections with their source page), which tells the agent this is relevance-ranked retrieval rather than exact lookup.

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?

One front-loaded sentence that leads with the verb and resource, then the corpus, then the return value. The long parenthetical enumeration of content categories is slightly heavy but earns its place by telling the agent what kinds of queries will hit.

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?

With no output schema, the description carries the burden of explaining returns and does so briefly and adequately. It is complete enough for a two-parameter read-only search; the only real omission is any explanation of the 'limit' parameter and ranking behavior.

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

Parameters2/5

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

Schema description coverage is only 50% — the 'query' parameter is documented in the schema with examples, but 'limit' (default 3, max 8) has no description anywhere. The description adds no parameter guidance at all: it never mentions the limit, its default, or how query phrasing (phrase vs. keywords) is interpreted, so it fails to compensate for the coverage gap.

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?

States a specific verb+resource ('Full-text search over the Ortho Earth documentation') and enumerates the corpus it covers, which immediately separates it from siblings like lookup_api, get_facts, and check_compat. It also says what comes back ('best matching sections with their source page'), so an agent can decide without opening the schema.

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 only implied: it is evidently the tool for prose/doc questions about the library itself, and the corpus list helps an agent recognize relevant questions. There is no explicit statement of when to prefer it over lookup_api or get_facts, and no exclusion for API-reference or facts lookups.

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.