Skip to main content
Glama

Horoscopes

get_horoscope
Read-only

Returns the Sun-sign horoscope Zodiacs publishes for a date: general, love or career for a day, or general for the week. With a birth date it adds a personal forecast for the week from that person's own chart, in dated lines. Each reading is dated and carries a "Reading confidence NN%" label that says how specific the details were, not the odds of an event. shareUrl is the link for sharing the reading. It fits a request for a daily or weekly horoscope or a reflective reading for a sign. A horoscope asked for with no sign named still belongs here: it opens with the sign left for the person to choose. Daily readings exist for the day before, the day of and the day after the current edition. Limits: no betting tips, sports picks, stock picks, investment timing, financial forecasts, election forecasts, health predictions or guaranteed outcomes, including when such a request mentions a horoscope. A request for one of those is not a request for this tool, not even as a first step: Zodiacs does not do this, and no horoscope is fetched for it. For a birth date under 18 there is no love or romance reading: the general reading stands in, with a note that says so. With no birth date it has no way to know the reader's age. It refuses a birth date less than 13 years ago. There is no horoscope for a named child under 13, meaning a particular child the request names or points to, such as someone's nine-year-old daughter, whatever the sign and with or without a birth date. A Sun sign on its own, with no name and no birth date, gets the general horoscope for that sign. Birth details are used for this answer only: never stored, logged or put in a link. Zodiacs sends no notifications and schedules nothing, so a reminder or a horoscope on a schedule is not a request for this tool either. Its results include a link to the sign-up page for the daily email.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_horoscope"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoA date such as 2026-10-08. Leave it out for the person's today.
signNoSun sign. Leave it out to let the person choose; never guess it.
zoneNoThe person's time zone, such as Asia/Bangkok or America/New_York. Without it, times are in UTC.
focusNoFor a daily reading: general (the default), love or career.
periodNoday (the default) or week.
birthDateNoOptional: the person's birth date, for a personal forecast of their week from their own chart. Not stored.
birthTimeNoOptional birth time on the local clock; needs birthZone. Not stored.
birthZoneNoOptional: the birthplace's time zone, needed with birthTime. Not stored.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations (readOnly, non-destructive, closed-world), the description discloses privacy handling (birth details used for this answer only, never stored, logged or linked), age rules (no love reading under 18 with a general substitute plus a note, hard refusal of birth dates under 13 years ago, no reading for a named child under 13), and the fact that no notifications or scheduling exist.

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?

It is front-loaded correctly, with the return shape stated first and the usage rules after. However, it runs long, repeats the exclusion point emphatically ("not a request for this tool, not even as a first step"), and spends its closing sentence on the sign-up email link even though an output schema exists.

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?

Given eight optional parameters, three enums, full schema descriptions, annotations and an output schema, the description covers everything an agent needs: scope of variants, age policy, privacy policy, and explicit non-use cases. No behavioral question relevant to invoking it correctly is left open.

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 cross-parameter meaning the schema does not: a birth date switches on a personal weekly forecast from the person's own chart rendered in dated lines, and focus love/career applies only to daily readings. The under-18 restriction on the love focus further constrains how parameters combine, which the per-field schema text cannot express.

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 opening sentence gives a specific verb and resource (returns the Sun-sign horoscope Zodiacs publishes) plus the scope of variants: daily general/love/career, weekly general, and a chart-based personal forecast when a birth date is supplied. The scope is clear enough to call the tool, but the sibling get_horoscope_period is never mentioned, so the boundary between this tool and that one is left to inference.

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?

It states positively when it fits (daily or weekly horoscope, reflective reading for a sign, and even a sign-less request, which opens with the sign left for the person to choose). It also states explicit exclusions: betting, sports, stock and investment timing, financial or election forecasts, health predictions, guarantees, and scheduled reminders, each declared not a request for this tool even as a first step.

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.