Skip to main content
Glama
Sign In

Perigee

by io.github.dlamarre-dev
OverviewDiscussionsAdmin

Ground track

perigee_ground_track
Read-only

The path on the ground below an Earth satellite over one or two orbits: a list of points (time, latitude, longitude, height) and a GeoJSON MultiLineString split at the antimeridian, ready for a map. Up to 360 points.

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": {
      "id": "<id>"
    },
    "name": "perigee_ground_track"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesObject 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. "25544" for the ISS.
langNoLanguage of names and texts (default en).
startNoISO 8601 UTC instant, e.g. 2026-12-01T00:00:00Z (default: now).
orbitsNoNumber of orbits (default 1).
pointsNoNumber of points (default 180 per orbit).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnlyHint, openWorldHint), so the description is free to spend its words on behavior — and it does, disclosing the exact return shape, the antimeridian split, and the 360-point ceiling. That is meaningful context an agent would otherwise have to discover by calling; only the time span covered by the samples is left implicit.

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?

One sentence with the payload front-loaded after the colon and zero filler. Every clause — ground path, orbit span, point fields, GeoJSON split, point cap — carries distinct 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 correctly absorbs the return-value burden by describing both representations and the antimeridian handling. What remains unstated — the coordinate reference frame and the exact time span implied by 'one or two orbits' — is minor for a read-only geometry tool.

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 the schema already explains id, lang, start, orbits and points in detail. The description echoes the orbit limit and point cap but adds no format or defaulting information beyond what the schema states. Baseline 3 applies.

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 resource — the ground path below an Earth satellite over one or two orbits — and even enumerates the return payload (point list plus GeoJSON MultiLineString). It implicitly separates itself from perigee_orbit and perigee_passes by describing a map-ready ground trace, but never names a sibling to make the distinction explicit.

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 phrase 'ready for a map' hints at the intended use case, and 'over one or two orbits' scopes the request. There is no statement of when to prefer this over perigee_orbit, perigee_passes or perigee_state, and no prerequisites or exclusions are given.

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