Skip to main content
Glama

AstroLogics

Zodiac horoscope

get_horoscope
Read-onlyIdempotent

Get the horoscope for one zodiac sign or for all twelve, for today, the current week, the current month or the year. Returns the reading plus numeric aspect scores, lucky factors and current transits.

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
signNoOne of aries, taurus, gemini, cancer, leo, virgo, libra, scorpio, sagittarius, capricorn, aquarius, pisces. Omit to get all twelve.
periodNoDefaults to today.
languageNoSet to "hi" to add Hindi (Devanagari) names next to the English ones, for answering in Hindi.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / language
      Added value: +{
      +  "description": "Set to \"hi\" to add Hindi (Devanagari) names next to the English ones, for answering in Hindi.",
      +  "enum": [
      +    "en",
      +    "hi"
      +  ],
      +  "type": "string"
      +}
  2. First observed

TDQS

A4/5.0
Behavior3/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 the safety profile is fully covered. The description adds genuine value by disclosing what comes back ('reading plus numeric aspect scores, lucky factors and current transits'), which matters because there is no output schema, but it says nothing about response size for the all-twelve case or caching/freshness of daily readings.

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 sentences, front-loaded with the action and scope, second sentence devoted entirely to return content. No filler or restatement of the title.

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?

All three parameters are optional and fully described in the schema, annotations cover the safety profile, and the description compensates for the missing output schema by listing the returned fields. The only minor omission is that it doesn't mention the Hindi-language option, which affects how the agent should present results to Hindi-speaking users.

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 would be 3, but the description earns credit by unpacking the ambiguous period enum values ('weekly'/'monthly'/'2026') into plain language: today, current week, current month, or the year. It doesn't explain the 'language' param, though the schema already documents it.

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?

States a specific verb and resource ('Get the horoscope') plus the exact scope: one sign or all twelve, across four period options. No sibling in the catalog returns sun-sign horoscope readings (the others are chart, dasha, panchang and dosha calculators), so the agent can route to it without opening the schema.

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?

The description implies usage by enumerating the choices available (sign, period), but it gives no explicit when-to-use or when-not-to-use guidance versus alternatives, and no prerequisites. The 'omit to get all twelve' behavior lives in the schema rather than the description.

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.

Resources