Skip to main content
Glama
astroway

astroway-mcp

Official

AI Natal Narrative

reports_ai_natal_narrative

Generate a personalized long-form natal chart narrative (markdown) based on birth details. Choose language, tone, and length to receive an AI-written interpretation of Sun, Moon, Ascendant, houses, and aspects.

Instructions

Long-form natal-chart narrative (markdown). Inputs: chart, language (21 codes), tone (warm/professional/concise), length (short/medium/long; ≤3200 tokens). Returns the narrative text plus model and token usage. AI grounded on the computed natal chart — Sun/Moon/Asc, 13 bodies, 12 houses, ≤25 major aspects.

[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.
languageNouk
toneNowarm
lengthNomedium
Behavior4/5

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

Annotations show readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true. The description adds context: it returns narrative text and token usage, and notes the token limit (≤3200 tokens). It does not contradict annotations.

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 paragraphs effectively convey purpose, inputs, outputs, and cost warning without redundancy. Every sentence adds value, and the structure is front-loaded with core information.

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?

For a generative AI report with no output schema, the description explains return values (narrative text, model, token usage) and the astrological grounding. It provides sufficient context for an agent to understand what to expect.

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?

Schema description coverage is 25% (only chart described). The description clarifies enum options for language (21 codes), tone (warm/professional/concise), and length (short/medium/long; ≤3200 tokens), adding value beyond the schema.

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 produces a 'long-form natal-chart narrative (markdown)', specifies inputs (chart, language, tone, length), and distinguishes it from other AI narrative tools by focusing on natal chart with specific astrological components (Sun/Moon/Asc, 13 bodies, 12 houses, ≤25 major aspects).

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?

The description includes a cost warning (250 credits, Tier 5) and advises to confirm with the user before invoking, indicating heavy usage. However, it does not explicitly compare to alternatives or state when not to use this tool.

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