Skip to main content
Glama

AstroWay Core astrology

Monthly Horoscope

astroway_horoscope_monthly
Read-onlyIdempotent

Monthly horoscope for a zodiac sign: the same shape as the daily one, over 30 days from date, with the month's ingresses, stations and lunar phases.

[Group: Horoscope] [Endpoint: POST /v1/horoscope/monthly] [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_monthly"
  }
}

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.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description contributes real extras: the cost (50 credits, Tier 3), the POST endpoint, and the fact that the response mirrors the daily payload. It says nothing about rate limits, latency, or what happens when `date` is omitted.

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?

A single front-loaded sentence with zero filler, followed by a compact metadata block for group, endpoint, required param and cost. Nothing is redundant, though the bracketed fields are terse rather than integrated into prose.

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; the cost and required parameter are stated and the 'same shape as daily' note sets expectations. The main residual gap is the undefined default for `date` and the partially undocumented parameter set.

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 coverage is 56%, and the description only clarifies `date` as the window start. Several parameters (sign enum, language, disclaimer_inline) are undocumented in both places, while style/fields/length/topics/precision are documented in the schema itself. It adds meaning for one parameter but does not compensate for the coverage gap.

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?

Names a specific resource (monthly horoscope for a zodiac sign) and pins the scope precisely: '30 days from `date`'. The 'same shape as the daily one' clause plus the explicit ingest/station/lunar-phase content distinguishes it from astroway_horoscope_daily, _weekly and _yearly without opening a schema.

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?

The period is implied by the name and the 30-day window, so an agent can infer when monthly beats daily or yearly. However, it never states the condition explicitly, gives no exclusions, and does not name the sibling to prefer for shorter or longer spans.

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