Skip to main content
Glama

Distance between two objects

perigee_distance
Read-only

Centre-to-centre distance between two objects at a date (km and astronomical units) and the light travel time, with the provenance of both positions, at one moment. Example: from "earth" to "mars".

Instructions

Centre-to-centre distance between two objects at a date (km and astronomical units) and the light travel time, with the provenance of both positions, at one moment. Example: from "earth" to "mars". Over a period, use perigee_distance_series; for the exact closest moment, perigee_close_approach.

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_distance"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesSecond object id from perigee_find (NORAD number, mission id, planet, "moon:<id>", "site:<id>", "launch:<id>", "star:<id>", "comet:<id>", "asteroid:<id>" or a dwarf planet name), e.g. "mars".
dateNoISO 8601 UTC instant, e.g. 2026-12-01T00:00:00Z (default: now).
fromYesFirst object id from perigee_find (NORAD number, mission id, planet, "moon:<id>", "site:<id>", "launch:<id>", "star:<id>", "comet:<id>", "asteroid:<id>" or a dwarf planet name), e.g. "earth".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.10.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds what the response contains (km, AU, light travel time, provenance for both positions), which matters because there is no output schema. It does not discuss error behavior for unknown object ids or whether the two positions come from different ephemeris sources, so it stops short of full disclosure.

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?

Three sentences, all front-loaded with the output contract first, then the usage routing, then the example. No filler and no repetition of the schema's parameter documentation.

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 read-only two-body distance query, the definition covers what is computed, the units returned, the time semantics (single moment, defaulting to now per the schema), and the two sibling alternatives. Together with full schema coverage, an agent has everything needed to call it correctly without an output schema.

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 each parameter already carries a detailed description including accepted id forms, so the baseline is 3. The description nudges above baseline by fixing the direction semantics with a concrete "from earth to mars" example and by noting the date is a single instant rather than a range.

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 computation (centre-to-centre distance between two objects), names the units (km and AU), and adds the secondary outputs (light travel time, provenance of both positions) at one moment. The concrete "earth" to "mars" example makes the resource unambiguous and separates it from the series and close-approach siblings.

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?

Explicitly routes the agent: "Over a period, use perigee_distance_series; for the exact closest moment, perigee_close_approach." Both alternatives are named with the condition that selects them, leaving nothing to inference about when this single-moment tool is the right call.

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