Skip to main content
Glama

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)]

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": {
      "sign": "<sign>"
    },
    "name": "astroway_horoscope_daily"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNo
signYes
styleNo`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.
fieldsNoCompact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response.
lengthNoWith `style: "plain"`: `short` (about 70-110 words a day) or `medium` (default, about 150-230).
topicsNoOnly these sections, in this order, in `sections` and in `horoscope`. Default all six.
languageNo
precisionNoCompact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.
disclaimer_inlineNo

Output Schema

NameRequiredDescriptionDefault
modelNo
languageNo
horoscopeNo
disclaimerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • removedOutput schema / properties / disclaimer / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / disclaimer / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / horoscope / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / horoscope / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / language / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / language / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / model / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / model / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  2. Changed3 schema fields changed
    • 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"
      +}
  3. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the read-only, idempotent, closed-world safety profile, so the description is free to add generation semantics. It does so usefully: the text is model-written from solar houses and transits, and `plain` content is authored once in English and translated so all 21 languages agree — a non-obvious behavioral trait. It omits the 50-credit Tier 3 cost implication and any note about determinism of repeated calls.

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 sentences, each front-loaded with the highest-value information: what is produced first, then the option semantics and return shape. No filler, no restatement of the tool name, and the backticked field names make it scannable.

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 and the description still summarizes the return payload, which is helpful but partly redundant. For a 9-parameter tool with only 56% schema coverage, several inputs (date default behavior, language selection, compact mode via `fields`/`precision`, `disclaimer_inline`) are left unexplained by both schema and description, which is a real gap.

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 56%, and the description reinforces `style`, `length`, and `topics` — including that `topics` controls both the size and section order. Four parameters (`date`, `language`, `fields`, `precision`, `disclaimer_inline`) get no explanation in the description; 'in 21 languages' hints at the language parameter but never states it or its default, and the compact-mode options are ignored.

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 and resource — a generated daily horoscope for a zodiac sign — plus the input basis (solar houses and the day's transits) and localization scope. It implies differentiation from astroway_horoscope_weekly/monthly/yearly through 'Daily' but never names or explicitly routes away from those siblings.

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?

It explains the meaning of `style: "plain"` versus the astrological mode and the `length`/`topics` trade-offs, which is genuine selection guidance at the option level. However, it gives no guidance on when to pick this tool over the weekly/monthly/yearly horoscope siblings, and no prerequisites or exclusions are stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources