Skip to main content
Glama

Distance over a period

perigee_distance_series
Read-only

Distances between two objects sampled evenly over a period (for a table or a chart), with the closest and farthest samples. The step limits their precision: for the exact closest moment, use 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>",
      "start": "<start>",
      "end": "<end>"
    },
    "name": "perigee_distance_series"
  }
}

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".
endYesISO 8601 UTC end.
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".
startYesISO 8601 UTC start.
stepsNoNumber of intervals (default 50, at most 100).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / from / description
      Added value: +"First 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\"."
    • addedInput schema / properties / to / description
      Added value: +"Second 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\"."
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover the read-only, open-world profile, and the description adds real value by disclosing that sampling precision is governed by the step and that the response includes closest and farthest samples. It does not discuss result limits or units, but the core behavioral tradeoff (approximation vs. exactness) is disclosed.

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?

Two short sentences with no filler; the output shape is front-loaded and the alternative-tool note follows as a natural qualifier. Nothing could be removed without losing information.

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?

With no output schema, the description appropriately summarizes the return (samples, closest and farthest). For a five-parameter, fully documented tool this is nearly complete, though units and behavior at the 100-step cap are left unstated.

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%, so the baseline is 3, but the description adds genuine meaning to the steps parameter by explaining it controls precision of the returned samples—an interpretation the schema's 'Number of intervals' does not convey. Other parameters rely on the schema.

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 computation (distance samples between two objects over a period) and the exact output shape (evenly spaced samples plus closest and farthest). It explicitly contrasts itself with perigee_close_approach, so an agent can separate them without opening either 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 gives a concrete use condition (building a table or chart) and names the alternative with the condition that selects it: use perigee_close_approach for the exact closest moment. That is explicit when-to-use plus routing guidance.

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