Skip to main content
Glama
astroway-mcp

astroway-mcp

Official
by astroway

Retrograde Periods

astroway_calendar_retrograde_periods
Read-onlyIdempotent

Retrieve planetary retrograde periods for a date range, including direct and retrograde stations, longitudes, and shadow start/end dates for selected planets.

Instructions

Retrograde periods of the planets in planetIds (default Mercury) within a date range: the two stations and their longitudes, plus shadowStart (the planet first reaches the longitude of its direct station) and shadowEnd (it regains the longitude of its retrograde station).

[Group: Calendar & Cycles] [Endpoint: POST /v1/retrograde-periods] [Required: startDate, endDate] [Cost: 50 credits (Tier 3)]

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": {
      "startDate": "<startDate>",
      "endDate": "<endDate>"
    },
    "name": "astroway_calendar_retrograde_periods"
  }
}

Input Schema

NameRequiredDescriptionDefault
endDateYes
planetIdsNo
startDateYes

Output Schema

NameRequiredDescriptionDefault
periodsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description is not required to cover that. It adds genuinely useful domain behavior via the shadowStart/shadowEnd definitions and the default-planet behavior, but says nothing about pagination, date-range limits, 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.

Conciseness4/5

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

The core purpose is front-loaded in the first sentence, followed by the bracketed operational metadata (group, endpoint, required params, cost) which earns its place for an agent budgeting calls. Slightly dense and run-on, but no wasted sentences.

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?

An output schema exists, so return values needn't be re-explained, and the description complements it with shadow-period definitions. For a simple 3-param read, the only material gap is usage routing and explicit date-format guidance.

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 0%, so the description carries the burden. It explains planetIds (with a Mercury default not present in the schema), but startDate/endDate are only implied by 'within a date range'; their format is left to the schema's regex pattern. Partial compensation, so a middling score.

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 resource (retrograde periods of planets) with a scoped input (planetIds, date range) and enumerates the exact output fields (stations, longitudes, shadowStart, shadowEnd). This level of specificity lets an agent tell it apart from stream/webhook retrograde tools (e.g. astroway_stream_retrograde_alerts) without consulting the schema.

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

Usage Guidelines2/5

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

There is no explicit when-to-use, when-not-to-use, or alternative routing. The only usage guidance is the 'default Mercury' parameter note, which is really parameter semantics, not usage. An agent gets no help deciding this over the streaming retrograde alerts siblings.

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

Deploy Server

Other Tools