Skip to main content
Glama
Sign In

Perigee

by io.github.dlamarre-dev
OverviewDiscussionsAdmin

Orbit

perigee_orbit
Read-only

Orbit of an object: perigee and apogee altitudes (periapsis/apoapsis), period, inclination, eccentricity, semi-major axis. Earth satellites: the mean elements of their published element set, with the orbit regime (LEO, MEO, GEO, HEO); other objects: instantaneous two-body elements around their centre at a date (default: the body they orbit; inclination on its equator, on the ecliptic around the Sun).

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

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.
dateNoISO 8601 UTC instant, e.g. 2026-12-01T00:00:00Z (default: now).
centreNoBody the orbit is around, e.g. "sun" for a planet or a probe.

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 already cover safety (readOnlyHint) and open-world scope, so the description is free to spend its words on the semantics that matter: Earth satellites yield mean elements of a published element set (cached-style, epoch-dependent), other objects yield instantaneous two-body elements at a date. It also discloses the reference plane convention (equator versus ecliptic around the Sun), which is real behavioral context an agent cannot get from annotations or schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the return payload, then the branching rule; every clause carries information and nothing is padded. The second sentence runs long and packs several clauses, which slightly hurts scanability but not correctness.

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?

There is no output schema, so the description correctly takes on the job of enumerating returned fields and does so thoroughly. Minor gaps remain: units for altitudes and period are not stated, and no indication of behavior for objects lacking a published element set.

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 baseline is 3, but the description adds genuine meaning: the 'centre' default is the body the object orbits, and that choice determines whether inclination is measured against the equator or the ecliptic. This interpretive rule for a parameter is exactly what the schema cannot express, so it exceeds the baseline.

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?

The description names the resource precisely and enumerates the returned quantities (perigee/apogee altitude, period, inclination, eccentricity, semi-major axis), and distinguishes two data sources: published mean elements for Earth satellites with a regime label versus instantaneous two-body elements for other objects. It stops short of differentiating from the sibling perigee_state, so an agent cannot tell from this text alone which of the two to call.

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?

Usage is only implied: the reader infers 'call this to get orbital elements', but nothing states when to prefer it over perigee_state, perigee_distance or perigee_events. No prerequisites or exclusions are given, and the Earth-satellite vs other-object branch is descriptive rather than a routing rule.

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