Skip to main content
Glama

Astrology explained

explain_astrology
Read-onlyIdempotent

Explains a basic astrology topic in plain words from Zodiacs' own pages, with links to them. It also answers whether two Sun signs are compatible, from that sign-pair page. It fits a "what does X mean" question: a sign and its traits, a planet, a planet in a sign or a house, the houses, aspects, retrogrades, Moon phases, the void-of-course Moon, eclipses, the rising sign, the Midheaven, the big three, cusps, the Saturn return, the solar return, elements, modalities, transits, synastry, Sun-sign pairs or the Chinese zodiac. For tarot, numerology, horary, Vedic astrology or another system Zodiacs does not cover, or when nothing matches, it returns found: false with the topics it does explain. A person's own placements belong to get_natal_chart. Two people with birth dates belong to get_compatibility, which compares their charts as partners, friends, family or colleagues; this tool takes two Sun signs with no birth dates. The sign of a calendar date belongs to get_birthday. A Sun-sign pair is answered as a romance reading for adults unless the topic includes the word friendship; the friendship answer is the element and modality pattern alone, with no romance. For anyone under 18 there is no love or romance reading, and the friendship reading takes its place. It takes no age or birth date, so it cannot know a reader's age. A guarantee about a relationship or anything else, a reading for a named child under 13, and a stock or lottery pick, an investment call, a bet, or an election or health forecast are not requests for this tool, not even as a first step: Zodiacs does not do these, and no explainer is fetched for them.

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": {
      "topic": "<topic>"
    },
    "name": "explain_astrology"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYesWhat to explain, in a few words: a sign (leo), a planet (Mercury), a placement (Moon in Scorpio, Jupiter in the 12th), the houses or one house (seventh house), aspects or one aspect (square), retrogrades or Mercury retrograde, Moon phases, the rising sign or a sign rising (Leo rising), the Midheaven, the big three, cusps, Saturn return, elements, modalities, transits, synastry, eclipses or the Chinese zodiac.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered; the description adds behavior the annotations cannot: failure mode ("returns found: false with the topics it does explain"), source attribution with outbound links, and the default that a Sun-sign pair is answered as an adult romance reading unless the word friendship appears, with the friendship answer limited to element/modality. The under-18 substitution rule and the hard-refusal list are non-obvious behavioral constraints an agent could not infer from any structured field.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and sibling routing are front-loaded, which is right, but the body is a dense block of run-on sentences with repeated topic inventories and some redundancy ("It takes no age or birth date, so it cannot know a reader's age" restates the preceding age policy). The information is mostly load-bearing, yet it would be clearer as a short structure of use / don't-use / fallback rather than a single paragraph.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter, read-only lookup with an output schema present, the description need not explain return values — and it still flags the found:false case, which is the one return detail that changes agent behavior. Combined with the topic coverage, sibling routing, and refusal rules, an agent has everything needed to call this correctly and to know when not to.

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 100% and the topic parameter's own schema description already enumerates accepted forms (sign, planet, placement, house, aspect, retrograde, rising, Midheaven, big three, cusps, Saturn return, elements, modalities, transits, synastry, eclipses, Chinese zodiac). The description repeats that inventory rather than adding syntax or formatting guidance beyond it, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb and resource ("Explains a basic astrology topic in plain words from Zodiacs' own pages") and then enumerates the topic space concretely — signs, planets, placements, houses, aspects, retrogrades, returns, synastry, Chinese zodiac. It explicitly differentiates from three named siblings: get_natal_chart for personal placements, get_compatibility for two full birth dates, get_birthday for a calendar date's sign.

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

Usage Guidelines5/5

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

Gives an explicit trigger ("It fits a 'what does X mean' question"), names the sibling each adjacent case belongs to, and states when-not conditions (tarot, numerology, horary, Vedic, or any uncovered system). It goes further with policy-level exclusions — guarantees, readings for named children under 13, stock/lottery/investment/bet/election/health forecasts — and says these are refused "not even as a first step," which prevents a plausible wrong first call.

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.