Skip to main content
Glama

Closest approach in space

perigee_close_approach
Read-only

The closest distance between two objects in space over a period (default 1 day, at most 1): when, how close (timed to a fraction of a second) and, for two Earth satellites, how fast they pass each other. For education only: public orbits are not precise enough for collision avoidance, and the answer says so. Distance in space, not closeness on the sky (use perigee_sky_conjunctions).

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": {
      "from": "<from>",
      "to": "<to>"
    },
    "name": "perigee_close_approach"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesSecond object id.
daysNoLength of the search in days (default 1).
fromYesFirst object id.
langNoLanguage of names and texts (default en).
startNoISO 8601 UTC instant, e.g. 2026-12-01T00:00:00Z (default: now).
time_zoneNoIANA time zone for local times, e.g. "Europe/Paris".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds substantial context beyond that: the default and maximum search window, sub-second timing precision, that relative speed is returned only for two Earth satellites, and that the answer itself carries a precision disclaimer — all non-obvious behavioral facts.

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 core purpose is front-loaded in the first clause, and each following sentence adds a distinct fact — timing/speed detail, the education disclaimer, and sibling disambiguation. No sentence is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter, read-only, open-world query with a fully documented schema and no output schema, the description supplies what is missing: what the result contains (time, distance, relative velocity), precision caveats, and scope limits. Nothing an agent needs to call it correctly is absent.

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%, so every parameter including from/to, start, days, lang and time_zone is already documented in the schema. The description restates the default/maximum period for days but adds nothing about the format or expectations of object ids. Baseline 3 is appropriate when the schema does the heavy lifting.

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 states a specific verb and resource — the closest distance between two objects in space over a period — and immediately disambiguates from the sibling perigee_sky_conjunctions by contrasting 'distance in space' with 'closeness on the sky'. An agent can tell exactly what computation this performs 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 Guidelines5/5

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

It names the alternative tool (perigee_sky_conjunctions) and the condition that selects it, and adds a clear use restriction ('for education only... not precise enough for collision avoidance'). Both the routing decision and the domain limit are explicit.

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.

Resources