Skip to main content
Glama

Retrograde Status

ephemeris_retrograde_status
Read-onlyIdempotent

Check whether one planet or all ten are retrograde at a given datetime, returning status, speed and station proximity for astrological or historical queries.

Instructions

Use this when the user asks 'is Mercury retrograde right now', 'was Mars retrograde when I was born' or 'which planets are retrograde at the moment'. Returns is_retrograde, speed and station proximity for one planet (Mercury is planet_id=2) or all ten.

CREDIT COST: 1 credit per planet (10 for all).

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": {
      "datetime": "<datetime>"
    },
    "name": "ephemeris_retrograde_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
datetimeYesISO 8601; zone required (`Z`/offset, or local time plus `timezone`).
timezoneNoIANA zone for a local datetime.
planet_idNo0 Sun, 1 Moon, 2–9 Mercury–Pluto. 1 credit; omit for all ten (10 credits).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv4.29.0
    • changedInput schema / properties / datetime / description
      Previous value: -"ISO 8601 datetime. A datetime with no zone is rejected; give a `Z` or ±HH:MM suffix, or a local time with the `timezone` argument. Date-only resolves to 12:00 UTC."New value: +"ISO 8601; zone required (`Z`/offset, or local time plus `timezone`)."
    • changedInput schema / properties / planet_id / description
      Previous value: -"Single planet ID (0=Sun, 1=Moon, 2=Mercury, 3=Venus, 4=Mars, 5=Jupiter, 6=Saturn, 7=Uranus, 8=Neptune, 9=Pluto). One planet costs 1 credit; omitted, all ten planets are checked for 10 credits."New value: +"0 Sun, 1 Moon, 2–9 Mercury–Pluto. 1 credit; omit for all ten (10 credits)."
    • changedInput schema / properties / timezone / description
      Previous value: -"IANA timezone (e.g. `America/Chicago`); required when the datetime is naive, ignored otherwise."New value: +"IANA zone for a local datetime."
  2. Changed2 schema fields changedv4.24.2
    • changedInput schema / properties / datetime / description
      Previous value: -"ISO 8601 datetime; zone required — a `Z`/±HH:MM suffix or the `timezone` argument. Date-only resolves to 12:00 UTC. Full rule: server `instructions`."New value: +"ISO 8601 datetime. A datetime with no zone is rejected; give a `Z` or ±HH:MM suffix, or a local time with the `timezone` argument. Date-only resolves to 12:00 UTC."
    • changedInput schema / properties / planet_id / description
      Previous value: -"Single planet ID (0=Sun, 1=Moon, 2=Mercury, 3=Venus, 4=Mars, 5=Jupiter, 6=Saturn, 7=Uranus, 8=Neptune, 9=Pluto). Pass this whenever the question names a planet — 1 credit. Omit only to sweep all ten — 10 credits."New value: +"Single planet ID (0=Sun, 1=Moon, 2=Mercury, 3=Venus, 4=Mars, 5=Jupiter, 6=Saturn, 7=Uranus, 8=Neptune, 9=Pluto). One planet costs 1 credit; omitted, all ten planets are checked for 10 credits."
  3. Changed3 schema fields changedv4.8.0
    • changedInput schema / properties / datetime / description
      Previous value: -"ISO 8601 date/time."New value: +"ISO 8601 datetime; zone required — a `Z`/±HH:MM suffix or the `timezone` argument. Date-only resolves to 12:00 UTC. Full rule: server `instructions`."
    • changedInput schema / properties / planet_id / description
      Previous value: -"Optional single planet ID (0-9). Omit for all planets."New value: +"Single planet ID (0=Sun, 1=Moon, 2=Mercury, 3=Venus, 4=Mars, 5=Jupiter, 6=Saturn, 7=Uranus, 8=Neptune, 9=Pluto). Pass this whenever the question names a planet — 1 credit. Omit only to sweep all ten — 10 credits."
    • addedInput schema / properties / timezone
      Added value: +{
      +  "description": "IANA timezone (e.g. `America/Chicago`); required when the datetime is naive, ignored otherwise.",
      +  "type": "string"
      +}
  4. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, and closed-world behavior. The description adds useful behavioral context by stating the returned fields and the credit cost per planet, though it does not discuss rate limits or auth requirements.

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?

The description is compact and front-loads the user intents, then the return values, then credit cost. Every sentence contributes useful selection or invocation context without filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only tool with full parameter documentation and rich annotations, the description provides enough context to call it correctly. It also compensates for the lack of an output schema by naming the key return fields.

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 input schema already documents datetime, timezone, and planet_id thoroughly. The description reinforces Mercury as planet_id=2 and notes all-ten behavior, but adds only marginal meaning beyond the structured schema.

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 states a specific resource and action through concrete user-question examples and names the returned fields. It clearly identifies retrograde status, but it does not explicitly differentiate itself from nearby siblings like electional_station_tracker or ephemeris_planet_position.

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 explicit when-to-use examples such as 'is Mercury retrograde right now' and 'was Mars retrograde when I was born'. It also explains the one-planet versus all-ten usage pattern, though it does not name alternatives or when not to use it.

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