Skip to main content
Glama

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

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_yearly"
  }
}

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
bodyNo
yearNo
titleNo
languageNo
solarReturnNo
profectionLordNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changed
    • removedOutput schema / properties / body / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / body / 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 / profectionLord / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / profectionLord / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • changedOutput schema / properties / solarReturn / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": {},
      -    "properties": {
      -      "date": {
      -        "anyOf": [
      -          {
      -            "type": "string"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ]
      -      }
      -    },
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": {},
      +    "properties": {
      +      "date": {
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      }
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedOutput schema / properties / title / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / title / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / year / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / year / type
      Added value: +[
      +  "number",
      +  "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

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful non-schema context — the endpoint and the 100-credit Tier 4 cost — but says nothing about latency, caching, or whether the result varies between calls despite idempotency.

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 well-formed sentence followed by a compact bracketed metadata block; the year scope is front-loaded and no sentence is filler. The metadata lines (Group/Endpoint/Required/Cost) are terse and skimmable rather than padding.

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?

With 9 parameters, an output schema, and rich annotations, the safety and return-value burden is largely offloaded elsewhere. The remaining gap is semantic: the description never clarifies what `date` means or how `sign`-only requests differ from date-anchored ones, which matters for a year-window generation tool.

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 adds nothing beyond 'Required: sign'. Critically, the `date` parameter has no schema description and no mention here, so an agent cannot tell whether it is a birth date or a reference date for the 12-month window — a material ambiguity for this tool.

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 — 'Generate a year-ahead horoscope (12-month window)' — and names the substantive content (transit cycles, solar return context, profection time-lord). The explicit '12-month window' scope cleanly separates it from the daily/weekly/monthly horoscope siblings, though none of them are named directly.

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 only implied by the scope word 'year-ahead'; there is no explicit 'use this when you want X instead of monthly/weekly'. The metadata block does supply a prerequisite ('Required: sign') and a cost signal, which is more than nothing but falls short of routing guidance against the four sibling horoscope tools.

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