Skip to main content
Glama
Sign In
Natal Chart Lab MCP

Natal Chart Lab MCP

by xucheng2024
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Retrograde periods

get_retrogrades
Read-only

Retrieve retrograde periods for Mercury through Pluto within a date range, including station times, signs, degrees, and shadow dates. Defaults to the next 12 months; filter by planet.

Instructions

Retrograde periods of Mercury through Pluto overlapping a date range, with station retrograde and direct times, signs and degrees, and pre-shadow and post-shadow dates. Covers retrogrades beginning 1950–2050. Defaults to the next 12 months.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_retrogrades"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoEnd date (ISO 8601). Defaults to 12 months after from.
fromNoStart date (ISO 8601). Defaults to now.
planetNoLimit to one planet

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered; the description adds genuinely new behavioral facts — the 1950–2050 coverage boundary and the default 12-month window — which prevent out-of-range or empty-result surprises. It stops short of noting ordering, result caps, or whether overlapping retrogrades are merged.

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?

Two sentences, zero filler, and the most decision-relevant facts (scope, return contents, coverage window, default) are front-loaded. Nothing repeats the tool name or title without adding 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 takes on the job of listing returned fields (station times, signs, degrees, shadow dates) and states the temporal coverage and default window. It is nearly complete for a three-optional-parameter read tool; only ordering and any result-count limits are unstated.

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% and each parameter is already documented, including the 'to' default of 12 months after 'from'. The description's 'Defaults to the next 12 months' and 'overlapping a date range' restate schema content rather than adding format or semantics, so the baseline of 3 applies.

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 opens with a specific verb and resource ('Retrograde periods of Mercury through Pluto overlapping a date range') and enumerates exactly what each entry contains: station retrograde/direct times, signs, degrees, and shadow dates. That is precise enough to separate it from a generic planet-positions tool without needing to open 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 Guidelines4/5

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

It gives concrete operating context: the catalog covers retrogrades beginning 1950–2050, and omitting parameters defaults to the next 12 months. What it does not do is route the agent away from alternatives (e.g., when to prefer this over get_planet_positions), so usage is clear but not comparative.

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