AstroWay Core astrology

Daily Horoscope

astroway_horoscope_daily

Read-onlyIdempotent

Daily horoscope for a zodiac sign in 21 languages, written by a model from that sign's solar houses and the day's transits. style: "plain" gives everyday words with no astrological terms, written once in English and translated so every language says the same; length (short, medium) and topics choose its size and sections. Returns sections (overview, love, career, health, finance, advice) and the same text as horoscope, plus computed transits with solar houses, aspects, events, energy (1-10 with its factors), lucky and compatibleSigns.

[Group: Horoscope] [Endpoint: POST /v1/horoscope/daily] [Required: sign] [Cost: 50 credits (Tier 3)]

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
`model`	No
`language`	No
`horoscope`	No
`disclaimer`	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

A3.9/5.0

Behavior4/5

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

Annotations already declare this a safe, idempotent read (readOnlyHint, idempotentHint, destructiveHint=false), so the safety profile is covered. The description adds genuinely useful behavior: the text is model-written from solar houses and transits, and 'plain' is authored once in English then translated so all languages agree. It omits cost (50 credits, Tier 3) and any rate/limit context.

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?

Purpose is front-loaded in the first clause, options second, return shape last; every sentence carries content. The return enumeration is long but scannable and no sentence is filler.

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 restating sections/horoscope/transits/energy is partly redundant, but nothing an agent needs to invoke the tool correctly is missing. The notable gap is the 50-credit Tier 3 cost and the absence of any sibling routing for the period variants.

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?

With schema coverage at 56%, the description compensates by explaining the two highest-friction parameters in prose: style 'plain' vs the default 'astro', and length (short/medium word ranges) plus topics controlling sections and order. It says nothing about date, fields, precision or disclaimer_inline, leaving those to a partially-documented schema.

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+resource+scope: 'Daily horoscope for a zodiac sign in 21 languages,' so an agent knows exactly what it produces. It never names the closely related siblings (astroway_horoscope_weekly, _monthly, _yearly, _compatibility), so the daily-vs-other-period distinction is left to the tool name alone.

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 the resource ('daily horoscope') rather than stated; there is no when-to-use/when-not guidance and no routing to the weekly/monthly/yearly variants that sit right beside it. The option-level guidance (style, length, topics) helps within the call but does not address tool selection.

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?