Skip to main content
Glama

Look up an Ortho Earth API

lookup_api
Read-onlyIdempotent

Returns the TypeScript declaration (with its doc comment) of an Ortho Earth API from the published types: createGlobe and its options (globe.d.ts), the map object it returns (globe-map.ts), and the MapLibre-compatible facade (maplibre.d.ts). Doc comments are partly in Japanese.

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": {
      "name": "<name>"
    },
    "name": "lookup_api"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesAn identifier, e.g. "createGlobe", "flyTo", "Map.addLayer", "GlobeOptions"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the bar is lower; the description still adds real context by naming the three source modules and warning that doc comments are partly in Japanese, which affects how the agent should read the output. It does not say what happens when the identifier is unknown, which matters given openWorldHint=false implies a fixed name set.

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?

Two sentences, front-loaded with the return value and followed by the scope of the published types; every clause carries information. The parenthetical file names are compact rather than redundant.

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 one-parameter read tool with no output schema, the description compensates by stating exactly what is returned (declaration plus doc comment) and flagging the Japanese doc comments. Only the behavior on an unknown identifier is left unexplained.

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 the schema already supplies four example identifiers, so the description need not explain the parameter. The list of source modules (globe.d.ts, globe-map.ts, maplibre.d.ts) weakly constrains which names are valid, but it does not map names to modules or state a lookup-failure behavior, so it adds little beyond the schema.

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?

Names a specific verb and resource ("Returns the TypeScript declaration ... of an Ortho Earth API") and enumerates the three published type sources it draws from, so the agent knows it is a type-lookup rather than a docs search. It does not explicitly name a sibling to contrast with (e.g. search_docs or get_facts), leaving that differentiation implicit.

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: an agent can infer this is the tool for exact type signatures because the return value is spelled out as the declaration plus doc comment. There is no explicit statement of when to prefer it over search_docs, nor any exclusion or prerequisite, so guidance stops at implication.

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.