Skip to main content
Glama
Sign In

Perigee

by io.github.dlamarre-dev
OverviewDiscussionsAdmin

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: use more steps for a precise closest 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. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuine value by disclosing the result content (sampled series plus the closest and farthest samples) and that precision is bounded by the step count — no output schema exists, so this is the only signal about what comes back. It still says nothing about units, ordering constraints, or failure modes.

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 compact sentences, the core purpose front-loaded and the tuning advice second. Every clause carries information; nothing is redundant.

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 read-only computation tool with five fully documented parameters and no output schema, the description covers purpose, sampling behavior, result contents, and precision control. It would be stronger with an explicit pointer to perigee_distance for single-instant queries and a note on units or start-before-end ordering.

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 goes beyond the schema's bare 'Number of intervals (default 50, at most 100)' by explaining the tradeoff: more steps yield a more precise closest approach. That is real semantic guidance an agent would not get from the schema alone.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific computation (distances between two objects sampled evenly over a period) and its output shape (closest and farthest samples). This separates it from perigee_distance in spirit, but the description never names the single-instant sibling, so an agent must infer the distinction.

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

Usage Guidelines3/5

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

The parenthetical '(for a table or a chart)' and the note about increasing steps for a precise closest approach imply the batch/series use case. However there is no explicit when-to-use rule, no exclusion versus perigee_distance for a single instant, and no statement of prerequisites such as object ids needing to come from perigee_find.

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

All Perigee toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources