Skip to main content
Glama
astroway-mcp

astroway-mcp

Official
by astroway

AI Year-Ahead Narrative

astroway_reports_ai_year_ahead_narrative

Generates a long-form year-ahead astrology report by combining natal chart context with monthly-clustered outer-planet transits for a chosen year, language, tone, and length.

Instructions

Long-form annual report. Combines natal context with the year's major outer-planet transits clustered by month. Inputs: chart, year (default = next year), language, tone, length (use long for full annual report).

[Group: AI Reports] [Endpoint: POST /v1/reports/ai/year-ahead-narrative] [Required: chart] [Cost: 250 credits (Tier 5)] ⚠️ Heavy — confirm with user before invoking.

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": {
      "chart": "<chart>"
    },
    "name": "astroway_reports_ai_year_ahead_narrative"
  }
}

Input Schema

NameRequiredDescriptionDefault
toneNowarm
yearNo
chartYesBirth 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 house-system letter, P by default; a name such as "Placidus" is refused, and the case matters because I and i are two different Sunshine systems.
lengthNomedium
languageNouk

Output Schema

NameRequiredDescriptionDefault
modelNo
tokensNo
narrativeNo
disclaimerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.6.1
    • changedInput schema / properties / chart / description
      Previous value: -"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."New value: +"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 house-system letter, P by default; a name such as \"Placidus\" is refused, and the case matters because I and i are two different Sunshine systems."
  2. Addedv1.6.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false and openWorldHint=true, so the description is not carrying the full load. It still adds real behavioral context beyond them: the POST endpoint, the 250-credit Tier 5 cost, and an explicit confirmation gate before invoking. It does not describe how long generation takes or what the output looks like, but the output schema covers returns.

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 prose sentences leading with the purpose, followed by compact bracketed metadata for group, endpoint, required field and cost. Every element earns its place and the most important information — what it produces and that it is expensive — is front-loaded.

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?

This is a costly generative tool with a nested chart object, and the definition covers purpose, required input, defaults, cost and a confirmation gate. Since an output schema exists, no prose about return values is needed. Nothing an agent needs in order to decide and invoke correctly appears to be missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With only 20% schema description coverage at the top level, the description has to compensate and largely does: it names chart, year (defaulting to next year, which the schema itself does not state), language, tone, and gives a usage rule for length ('use long for full annual report'). The nested chart object is heavily documented in the schema, so the remaining gap is minor rather than crippling.

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?

States a specific artifact and method: a 'Long-form annual report' that combines natal context with the year's major outer-planet transits clustered by month. That is more than a restatement of the name and lets an agent tell it apart from a monthly or natal narrative. It stops short of naming an explicit alternative, so it lands at 4 rather than 5.

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

Usage Guidelines3/5

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

The description gives a procedural directive — 'Heavy — confirm with user before invoking' — plus the required input and the cost, which is genuine usage guidance. What it does not give is when to pick this over sibling annual-transit or monthly-narrative tools. Usage is therefore implied rather than routed.

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