Skip to main content
Glama

Zodiac Compatibility

Daily horoscope

get_daily_horoscope
Read-onlyIdempotent

Returns a sign's reading for a UTC date, built from that day's real planet positions: the day's reading with the transits it uses, a one-line preview of the next day, and a line for each of the following seven days.

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": "get_daily_horoscope"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoUTC date as YYYY-MM-DD, from 1900 to 2100. Today's UTC date when omitted.
signYesZodiac sign, such as Gemini or Scorpio, in any letter case.

Output Schema

NameRequiredDescriptionDefault
itemYes
viewYes
requestNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/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. Beyond that, the description adds genuine context: the reading is derived from that day's real planet positions and includes the transits used, which tells the agent results are computed rather than static text. It doesn't address determinism across calls or rate limits, keeping it short of a 5.

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

Conciseness5/5

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

A single front-loaded sentence with a colon-delimited list of outputs; nothing is padding. It does restate return content that the output schema already covers, but that restatement is compact and helps an agent understand the shape at a glance.

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?

With an output schema, full parameter documentation, and complete annotations, the description supplies what's needed: provenance of the reading and the span of days returned. Minor gaps remain, such as behavior for an unrecognized sign or how the week-ahead lines differ from the next-day preview, but nothing blocks correct invocation.

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 description coverage is 100%, and the schema already documents the YYYY-MM-DD format, the 1900-2100 range, and the today-default. The description reinforces the UTC framing of the date but adds no syntax or constraint beyond what the schema supplies, so baseline 3 applies.

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 pairs a specific verb ('Returns') with a precise resource ('a sign's reading for a UTC date') and even enumerates the payload: today's reading, the transits used, a next-day preview, and seven following days. It never names a sibling to contrast against, but its resource is visibly distinct from the natal-chart and sign-finder siblings, so an agent can select it without ambiguity.

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 resource name and the notion of a 'daily' reading; there is no explicit statement of when to prefer this over get_sign_profile or find_sun_sign, nor any exclusion. The defaulting rule for the date lives in the schema, not the description. Adequate for an obviously scoped tool, but guidance is inferred rather than stated.

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.