astroway-mcp

Official

Overview Schema Source Related Servers Discussions Admin

Generate Year-Ahead Transit (PDF or HTML)

astroway_reports_transit_yearly

Generate a year-ahead transit calendar PDF grouped by month, listing outer-planet aspects to natal positions within 0.5° orb. Use it to plan key dates for a client's coming year.

Instructions

Render a year-ahead transit calendar PDF grouped by month. Includes major aspects (conjunction, sextile, square, trine, opposition) of outer planets (Mars through Pluto) to natal positions, with 0.5° max orb. Defaults to next calendar year if year omitted.

[Group: Reports] [Endpoint: POST /v1/reports/transit-yearly] [Required: chart] [Cost: 5,000 credits (Tier 7)] ⚠️ Premium — ~50% of free monthly budget. Confirm with user before invoking.

Input Schema

Name	Required	Description
`year`	No
`chart`	Yes	Birth data for a single natal chart. Required: date (YYYY-MM-DD), time (HH:mm:ss), latitude and longitude in decimal degrees. The short forms lat, lon, lng and tz are rejected with 400 INVALID_FIELD; pass the full names. timezoneOffset is hours from UTC and defaults to 0, meaning UTC; send timezone instead (an IANA name such as Europe/Kyiv, or auto) and the offset for that date is worked out, summer time included. city is a display label only: nothing here geocodes it, so it never stands in for coordinates. houseSystem is a single Swiss Ephemeris letter, P by default; a name such as "Placidus" is refused, and the case matters because I and i are two different Sunshine systems.
`language`	No
`whitelabel`	No

Output Schema

Name	Required	Description	Default
`url`	No
`expires_at`	No
`page_count`	No
`byte_length`	No
`duration_ms`	No
`storage_key`	No

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.6.0Oct 24, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover read-only/mutation and openness, so the description's main added value is the pricing disclosure: 5,000 credits, Tier 7, ~50% of free monthly budget, plus a confirm-before-invoking instruction — genuinely useful pre-call behavior. Minor gap: the title says 'PDF or HTML' while the description says PDF only, leaving the output format ambiguous.

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?

Three tight sentences: what is produced, what it contains, then the default. The bracketed group/endpoint/required/cost lines are scannable and front-load the decision-critical premium warning.

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 need not be described, and the credit cost and required input are covered. What remains unaddressed is the PDF-vs-HTML output choice and any guidance on the whitelabel/language options for a 4-parameter, premium-priced report.

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 only 25%, so the description ideally compensates, but it only explains the `year` fallback and that `chart` is required (already in the schema). `language` and the large `whitelabel` object are left entirely to the schema, so meaningful compensation is missing.

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?

States a specific verb and deliverable: render a year-ahead transit calendar PDF grouped by month. It also names the exact technical scope (outer planets Mars–Pluto, five major aspect types, 0.5° orb), which lets an agent distinguish it from generic transit/forecast siblings without opening 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?

Gives a clear usage condition (year defaults to next calendar year if omitted) and an explicit precondition to confirm with the user because of cost. It does not name a cheaper alternative (e.g. transit calendar or AI transit narrative) for the agent to route to instead, so it stops short of full when/when-not guidance.

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

Deploy Server