Skip to main content
Glama
Sign In

Horoscope

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Daily Horoscope

daily_horoscope
Read-onlyIdempotent

Get the daily horoscope for a zodiac sign. Returns the prediction text for a given day (today, tomorrow, yesterday, or a specific YYYY-MM-DD date). Useful for "what is my horoscope today" style questions.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

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

Input Schema

NameRequiredDescriptionDefault
dayNoDay to fetch. One of TODAY, TOMORROW, YESTERDAY, or a date in YYYY-MM-DD format. Defaults to TODAY.
signYesZodiac sign (case-insensitive). One of: aries, taurus, gemini, cancer, leo, virgo, libra, scorpio, sagittarius, capricorn, aquarius, pisces.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "sign": "aries"
+  },
+  {
+    "day": "2025-01-15",
+    "sign": "pisces"
+  },
+  {
+    "day": "TOMORROW",
+    "sign": "leo"
+  }
+]
  2. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false, covering safety and idempotency. Description adds that it returns 'prediction text' and specifies valid day values, which is useful but not extensive beyond annotations.

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?

Two concise sentences with no unnecessary words. Front-loaded with purpose and supported by examples. Every sentence adds value.

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 simple read-only tool with no output schema, the description adequately conveys purpose, input variations, and return type ('prediction text'). Completeness is high given the tool's simplicity and rich annotations/schema.

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% with clear descriptions and examples for both parameters. The description does not add significant new meaning beyond the schema, but it reinforces the day variations and zodiac sign list. Baseline of 3 is appropriate.

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?

Clear verb 'Get' and specific resource 'daily horoscope for a zodiac sign'. Distinguishes from siblings (weekly_horoscope, monthly_horoscope) by focusing on daily granularity. Includes examples of day values.

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

Usage Guidelines4/5

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

Explicitly states usefulness for 'what is my horoscope today' queries and lists day options (today, tomorrow, yesterday, date). Does not explicitly mention when not to use it or name alternatives, but the context of daily vs weekly/monthly sibling tools provides implicit guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Horoscope toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources