Skip to main content
Glama
astroway

astroway-mcp

Official

AI Year-Ahead Narrative

reports_ai_year_ahead_narrative

Generate a long-form annual astrological report combining your natal chart with monthly clusters of major outer-planet transits.

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] [Cost: 250 credits (Tier 5)] ⚠️ Heavy — confirm with user before invoking.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chartYesBirth data for a single natal chart. Required: date (YYYY-MM-DD), time (HH:mm:ss). Defaults to lat/lon/tz=0 if omitted; pass real values for accurate computation.
yearNo
languageNouk
toneNowarm
lengthNomedium
Behavior4/5

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

Discloses the tool is expensive (250 credits) and advises confirmation, going beyond the openWorldHint annotation. However, it does not describe the return format or any side effects other than cost.

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?

Extremely concise with no wasted words; the purpose, inputs, and cost warning are front-loaded in a short, clear format.

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

Completeness3/5

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

Lacks details on output format and the exact meaning of 'outer-planet transits clustered by month.' For a complex, heavy tool, more background on what the report contains would be beneficial.

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?

Adds some value by noting year defaults to next year and that length 'long' gives a full report, but given low schema coverage (20%), it does not adequately explain the chart object or other parameters in depth.

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 clearly states it is a 'Long-form annual report' that 'combines natal context with the year's major outer-planet transits clustered by month,' which is specific and distinct from sibling tools like reports_ai_monthly_narrative or reports_ai_natal_narrative.

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?

Provides explicit guidance to use the 'long' length for a full annual report and includes a cost warning ('Heavy — confirm with user before invoking'). However, it does not explicitly list when not to use or mention alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/astroway/astroway-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server