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.

Instructions

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 1000).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.10.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already establish readOnlyHint and openWorldHint, so the safety profile is covered. The description adds useful behavioral context by disclosing that results are evenly sampled and include closest and farthest samples, and that step size limits precision.

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 tightly written sentences with no filler. The core sampling behavior is front-loaded, followed immediately by the precision caveat and alternative tool.

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 tool with no output schema, the description conveys the essential return content: sampled distances plus closest and farthest samples. It does not specify output shape or units, but enough is provided to select and invoke the tool correctly.

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 parameter meanings are already well documented. The description adds meaning beyond the schema by explaining that steps controls sampling precision and by directing exact-moment use to another tool.

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 and operation: distances between two objects sampled evenly over a period. It explicitly distinguishes itself from perigee_close_approach for exact closest-moment queries, so an agent can identify its role 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?

Names the intended use for a table or chart and explicitly routes exact closest-moment requests to perigee_close_approach. The precision tradeoff from steps is also stated, leaving little ambiguity about when to use this tool.

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