Skip to main content
Glama
astroway-mcp

astroway-mcp

Official
by astroway

AI Natal Narrative

astroway_reports_ai_natal_narrative

Generate a long-form natal-chart narrative in Markdown from a computed chart, with selectable language, tone, and length for AI astrology reports.

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] [Endpoint: POST /v1/reports/ai/natal-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_natal_narrative"
  }
}

Input Schema

NameRequiredDescriptionDefault
toneNowarm
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
toneNo
modelNo
lengthNo
tokensNo
languageNo
narrativeNo
disclaimerNo
duration_msNo

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

A3.7/5.0
Behavior4/5

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

Annotations only cover safety flags (readOnly=false, openWorld=true, idempotent=false, destructive=false); the description adds the materially important traits an agent needs: a 250-credit cost, a human-confirmation requirement, a token ceiling of ≤3200 for the output, and the fact that the model is grounded on a computed chart rather than free-form. It stops short of latency, failure modes, or whether the same chart input yields stable output (relevant given idempotentHint=false).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the one-line purpose, then a compact Inputs/Returns/grounding sentence, then bracketed metadata for group, endpoint, required field and cost. Nearly every line earns its place; the only mild redundancy is repeating 'chart' as both an input and a [Required] marker, plus boilerplate endpoint text.

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 the description need not detail return shape, and it still briefly notes narrative text plus model and token usage. Cost, required input, grounding scope and the token cap are all covered for a complex nested-chart AI call; the missing piece is routing guidance among the many sibling report tools.

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 low at 25%, but the heavy nested chart object is itself richly documented in the schema, so the description's main added value is the ≤3200-token ceiling tied to length and the enumeration of the language/tone/length option sets. Those enums are already fully listed in the schema, so the description mostly restates rather than deepening parameter meaning.

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 verb and resource: a long-form natal-chart narrative returned as markdown, with the exact grounding scope (Sun/Moon/Asc, 13 bodies, 12 houses, ≤25 aspects). It does not name or differentiate itself from near-siblings such as astroway_ai_interpret_natal or astroway_reports_natal, so an agent cannot tell from this text alone which natal-report tool to pick.

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?

Gives real invocation guidance in the metadata block: the only required input is chart, the call costs 250 credits at Tier 5, and it is flagged 'Heavy — confirm with user before invoking.' However it never says when to use this versus the other natal narrative/interpretation siblings, and offers no exclusions or preconditions beyond the cost warning.

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