Skip to main content
Glama

Find an object

perigee_find
Read-only

Looks up objects by name or identifier (English or French, accents optional): planets, moons, missions beyond Earth orbit, featured science satellites, any active Earth satellite (by name, NORAD or COSPAR id), landing and launch sites…

Instructions

Looks up objects by name or identifier (English or French, accents optional): planets, moons, missions beyond Earth orbit, featured science satellites, any active Earth satellite (by name, NORAD or COSPAR id), landing and launch sites, named stars. Returns the ids the other tools take: start here when you only have a name.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results (default 10).
queryYesName or identifier to look up, e.g. "ISS", "Voyager 1", "25544", "Mars", "Apollo 11".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.10.0

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and open-world profile is covered. The description adds useful behavior beyond that: multilingual and accent-insensitive matching, identifier-format tolerance (NORAD, COSPAR), and the fact that results are ids consumable by other tools. It does not mention result ranking, ambiguity handling, or what happens when a name matches multiple objects.

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 resource list and ending with the actionable routing hint. The long enumeration in the first sentence is justified because it defines scope, though it is dense enough to slow scanning slightly.

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 read-only, two-parameter lookup with no output schema, the definition covers inputs, accepted formats, scope, and the follow-up path to sibling tools. Missing only disambiguation behavior for ambiguous names, which matters given the breadth of object types listed.

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

Parameters4/5

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

Schema coverage is 100% and both params are documented, so the baseline is 3. The description goes beyond the schema by explaining that the query accepts English or French names and accents are optional, plus the identifier formats, which the schema's examples only imply.

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 names a specific verb ("Looks up") and enumerates the resource classes it covers: planets, moons, missions, active Earth satellites by name/NORAD/COSPAR, landing and launch sites, named stars. It also distinguishes itself from the sibling accessor tools by stating it "Returns the ids the other tools take".

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

Usage Guidelines5/5

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

It gives explicit routing guidance: "start here when you only have a name." That tells the agent when this tool is the right entry point versus the perigee_object/perigee_state lookups that need an id. No exclusion of alternatives is spelled out by name, but the entry-point rule is unambiguous.

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