Skip to main content
Glama

Monthly, yearly and weekly horoscopes

get_horoscope_period
Read-only

Returns the Sun-sign reading Zodiacs publishes for a month, a year, or a love or career week, together with that period's sky for the sign: planets changing sign, turning retrograde or direct, new and full Moons and eclipses, placed in the sign's solar houses. A week adds that focus's daily readings. The forecast carries a "Reading confidence NN%" label that says how specific the details were, not the odds of an event. It fits a request for a sign's month or year, or for a love or career week. Monthly readings are published from the first of each month, and yearly readings exist for 2026 and 2027. When a reading is not published it says so and still gives the sky. A month's sky leaves out the Moon's sign changes. A week is for love or career only; a general week and a single day belong to get_horoscope. Limits: focus love is a romance reading for adults, so for anyone under 18 there is no love or romance reading. No betting tips, sports picks, stock picks, investment timing, election forecasts, health predictions or guaranteed outcomes. It takes no birth date, so it cannot know a reader's age. There is no horoscope for a named child under 13, meaning a particular child the request names or points to, whatever the sign. A Sun sign on its own, with no name and no birth date, gets the general reading for that sign. Its results include a link to the sign-up page for the daily email. Its times for a slow planet's sign change carry the same limit as get_upcoming_events.

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>",
      "period": "<period>"
    },
    "name": "get_horoscope_period"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoAny day in the month, year or week wanted, such as 2026-12-01 for December 2026. Leave it out for the person's current month, year or week.
signYesSun sign. Never guess it; ask the person if they have not said.
zoneNoThe person's time zone, such as America/New_York, so the period and dates are their own. Without it, UTC.
focusNogeneral (the default), love or career. For a week it adds that focus's daily readings; for every period it keeps the sky events that bear on it.
periodYesmonth, year or week.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Beyond readOnly/destructive annotations it discloses real behavior: an unpublished reading still returns the sky, a month's sky omits the Moon's sign changes, weeks add daily focus readings, the 'Reading confidence NN%' label describes specificity rather than event odds, and results carry an email sign-up link. It also flags that slow-planet sign-change times inherit the precision limit of get_upcoming_events. The one gap is that it never says whether repeated calls or different dates are idempotent, despite idempotentHint=false.

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?

The first sentence front-loads purpose and scope precisely, and most following sentences carry a distinct operative rule (publication windows, week-vs-day routing, minor-safety limits). It is dense and long for a five-parameter read tool, with a policy list (betting, stocks, elections, health) that is useful but not tightly worded.

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?

The tool takes no birth date, so the description pre-empts the obvious agent confusion by explaining that a bare Sun sign gets the general reading, that a named child under 13 has no horoscope, and that no love reading exists for under-18s. With an output schema present, no return-value detail is required, and nothing an agent needs to call this correctly is missing.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: omitting the date yields the current period, focus changes what a week returns and which sky events are kept, and yearly values are bounded to 2026-2027. That constrains enum usage in a way the schema alone does not.

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: returns the Sun-sign reading for a month, year, or love/career week, plus that period's sky placed in the sign's solar houses. It explicitly carves out the sibling boundary — 'A week is for love or career only; a general week and a single day belong to get_horoscope' — so an agent can route without opening either schema.

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?

States positively when it fits ('a request for a sign's month or year, or for a love or career week') and negatively when it does not, naming the alternative tool for general weeks and single days. It also gives the availability windows (monthly from the first of each month, yearly only for 2026 and 2027) and the focus constraint that love is romance for adults with no reading under 18.

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.