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 7): when, how close (timed to a fraction of a second) and, for two Earth satellites, how fast they pass each other.

Instructions

The closest distance between two objects in space over a period (default 1 day, at most 7): 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 observedv1.10.0

TDQS

A4.2/5.0
Behavior4/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 real value on top by disclosing the default and maximum search window (1 day, capped at 7), the sub-second timing precision of the result, and the fact that the response itself carries the educational-use disclaimer. It stops short of describing pagination or the concrete response shape.

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 core definition, then the disambiguation pointer last. The parenthetical precision detail and the disclaimer both earn their place, though the opening sentence is dense enough to require a second read.

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?

With no output schema, the description still tells the agent what comes back (when, how close, how fast) and what the response asserts about accuracy. Combined with full schema coverage and annotations, nothing an agent needs to call this correctly is missing.

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 description coverage is 100%, so all six parameters including from/to, days, start, lang and time_zone are already documented in the schema. The description only echoes the period default and cap that the schema's minimum/maximum already encode, adding essentially no new parameter meaning.

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 resource (closest distance between two objects over a period) and enumerates the returned quantities: time of closest approach, distance, and relative speed for two Earth satellites. It explicitly contrasts itself with perigee_sky_conjunctions, so an agent can separate it from that sibling without opening a schema.

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

Usage Guidelines4/5

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

The final clause names the alternative (perigee_sky_conjunctions) and the condition that selects it — angular closeness on the sky versus true distance in space. It also scopes the tool with a clear 'education only, not for collision avoidance' caveat, but gives no guidance relative to the other distance-oriented siblings such as perigee_distance or perigee_distance_series.

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