AstroWay Core astrology

Yearly Horoscope

astroway_horoscope_yearly

Read-onlyIdempotent

Generate a year-ahead horoscope (12-month window) with major transit cycles, solar return chart context, and time-lord (profection) for the year.

[Group: Horoscope] [Endpoint: POST /v1/horoscope/yearly] [Required: sign] [Cost: 100 credits (Tier 4)]

Input Schema

Name	Required	Description
`date`	No
`sign`	Yes
`style`	No	`astro` (default) names the planets, houses and aspects behind each point. `plain` uses everyday words with no astrological terms, and is written once in English and translated, so every language says the same thing. Daily, weekly and monthly.
`fields`	No	Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response.
`length`	No	With `style: "plain"`: `short` (about 70-110 words a day) or `medium` (default, about 150-230).
`topics`	No	Only these sections, in this order, in `sections` and in `horoscope`. Default all six.
`language`	No
`precision`	No	Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.
`disclaimer_inline`	No

Output Schema

Name	Required	Description	Default
`body`	No
`year`	No
`title`	No
`language`	No
`solarReturn`	No
`profectionLord`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 21, 2026

addedInput schema / properties / length

Added value: +{
+  "description": "With `style: \"plain\"`: `short` (about 70-110 words a day) or `medium` (default, about 150-230).",
+  "enum": [
+    "short",
+    "medium"
+  ],
+  "type": "string"
+}

addedInput schema / properties / style

Added value: +{
+  "description": "`astro` (default) names the planets, houses and aspects behind each point. `plain` uses everyday words with no astrological terms, and is written once in English and translated, so every language says the same thing. Daily, weekly and monthly.",
+  "enum": [
+    "astro",
+    "plain"
+  ],
+  "type": "string"
+}

addedInput schema / properties / topics

Added value: +{
+  "description": "Only these sections, in this order, in `sections` and in `horoscope`. Default all six.",
+  "items": {
+    "enum": [
+      "overview",
+      "love",
+      "career",
+      "health",
+      "finance",
+      "advice"
+    ],
+    "type": "string"
+  },
+  "maxItems": 6,
+  "minItems": 1,
+  "type": "array"
+}

First observedOct 5, 2026

TDQS

B3.2/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, non-open-world), so the bar is lower. The description adds genuinely useful operational context: the POST endpoint, the required parameter, and a concrete cost tier (100 credits, Tier 4), which the agent cannot derive from annotations.

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?

One dense but front-loaded sentence delivers the core purpose, followed by clearly structured bracketed metadata (group, endpoint, required, cost). No filler, though the parameter guidance one would expect from a 9-param tool is simply absent rather than trimmed.

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?

An output schema exists, so return values need not be described, and annotations carry the safety profile. Still, for a 9-parameter tool with 56% schema coverage, the definition leaves the agent without guidance on parameter usage or on how it differs from the monthly/report siblings.

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

Parameters2/5

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

Schema description coverage is only 56%, and the description mentions nothing beyond 'sign' as required. It does not explain how 'date' anchors the 12-month window, or what language/style/topics/length do for a yearly horoscope. The schema's own rich text covers some params, but the description fails to compensate for the rest.

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?

The description gives a specific verb (generate) plus resource (year-ahead horoscope), scope (12-month window), and enumerates the analytical content (transit cycles, solar return context, profection). The 'year-ahead (12-month window)' phrasing implicitly separates it from the daily/weekly/monthly horoscope siblings, though none is named explicitly.

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

Usage Guidelines2/5

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

There is no statement of when to use this tool versus astroway_horoscope_monthly or astroway_reports_ai_year_ahead_narrative, nor any prerequisite or exclusion. Only the [Required: sign] and cost lines hint at invocation conditions.

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

All AstroWay Core astrology tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?