Skip to main content
Glama
astroway-mcp

astroway-mcp

Official
by astroway

AI Monthly Narrative

astroway_reports_ai_monthly_narrative

Generate a single-month AI forecast from a natal chart using fast and slow planet transits, with configurable tone, length and language for monthly readings.

Instructions

Single-month forecast. Tighter scope than year-ahead: uses fast and slow planet transits within the month. Inputs: chart, year, month (1-12), language, tone, length.

[Group: AI Reports] [Endpoint: POST /v1/reports/ai/monthly-narrative] [Required: chart, year, month] [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>",
      "year": "<year>",
      "month": "<month>"
    },
    "name": "astroway_reports_ai_monthly_narrative"
  }
}

Input Schema

NameRequiredDescriptionDefault
toneNowarm
yearYes
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.
monthYes
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

A3.7/5.0
Behavior4/5

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

Annotations declare openWorldHint=true and idempotentHint=false but say nothing about cost or repeat-call consequences; the description fills that gap with "Cost: 250 credits (Tier 5)" and the instruction to confirm with the user first, which explains why repeated calls are not free. The endpoint line adds transport context. It stops short of 5 because it does not say what happens on failed/partial generation or whether credits are consumed on error.

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 scope statement, then the differentiator, then the input list, then bracketed operational metadata — a clean scan order with no filler prose. The input list is mildly redundant with the schema, which keeps it from a 5.

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 critical operational fact (heavy credit cost requiring user confirmation) is disclosed, as is the endpoint and required fields. Remaining gaps are minor — no note on failure behavior or on how tone/length affect output size/cost.

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 17%, so the description would ideally carry more weight, but for the hardest parameter (chart) the schema itself is extensively documented. The description's own contribution is a bare list of the six inputs ("chart, year, month (1-12), language, tone, length"), which mostly restates the schema and adds no meaning for tone, length, or language beyond their enums and defaults. Baseline 3 fits given the nested chart schema does the heavy lifting.

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?

"Single-month forecast" gives a specific verb-like resource and scope, and the description explicitly contrasts it with the year-ahead report ("Tighter scope than year-ahead"), letting an agent separate it from astroway_reports_ai_year_ahead_narrative and the other AI narrative siblings. It never states outright that it generates a written narrative report, relying on the tool name/title for that, so it falls just short of 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?

Usage is implied by scope (a within-month forecast rather than a year-ahead one) and reinforced by the operational warning "Heavy — confirm with user before invoking," which is real invocation guidance. However there is no explicit when-not guidance, no statement of prerequisites (e.g., a valid natal chart is required), and no pointer to cheaper alternatives such as astroway_horoscope_monthly.

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