Skip to main content
Glama

Sunlight and shadow

perigee_shadow
Read-only

Determine whether a satellite or spacecraft is in sunlight, penumbra, or umbra and when it will enter or leave shadow, explaining sudden fading during night-sky passes.

Instructions

Whether an object is in sunlight, in the penumbra or in the umbra of the body it orbits (Earth satellites: the Earth's shadow; lunar and Martian orbiters: the Moon's or Mars'), and when it next enters and leaves the shadow (default: over two orbits, at most 48 hours). Explains why a satellite crossing the night sky suddenly fades out.

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

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).
langNoLanguage of names and texts (default en).
hoursNoLength of the search in hours (default: two orbits).
centreNoBody casting the shadow (default: the one the object orbits).
time_zoneNoIANA time zone for local times, e.g. "Europe/Paris".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.10.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnly and openWorld, and the description usefully adds the default time window and the physical meaning of the three shadow states. However it says nothing about return shape, cost of computation, or behavior when the object never enters shadow (e.g., high-orbit objects) — a meaningful gap for a tool whose answers can be 'no shadow events'.

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 core answer and efficient overall, but the long opening sentence with its nested parenthetical about Earth/Moon/Mars shadows is heavier than needed. The 48-hour default is stated once in the premise and echoed in the parameter list, a small redundancy.

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 six parameters, one required, and no output schema, the definition supplies the essentials: what is measured, the default horizon, and which body casts the shadow. It is slightly thin on what a response looks like and on the no-event case, but the entry/exit phrasing covers the main return semantics adequately.

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 coverage is 100%, so baselines to 3; the description largely restates schema facts (default of two orbits, the 48-hour cap) rather than adding syntax or edge-case guidance. It does imply that 'centre' defaults to the orbited body, but the schema already states that.

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 names a specific quantity (illumination state: sunlight, penumbra, umbra) plus the temporal part (next entry and exit times), which is concrete enough that an agent can separate this from perigee_passes or perigee_sky without inspecting other schemas. The closing line tying it to a satellite fading out during a night pass anchors the resource further.

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

Usage Guidelines4/5

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

It gives a clear use case (explaining why an object fades) and states the default search horizon of two orbits / 48 hours, which tells an agent how far ahead answers extend. It does not name alternatives or state when another tool would be preferable, so it stops short of explicit routing.

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