Skip to main content
Glama
AstroChalit MCP Server

AstroChalit MCP Server

get_horoscope

Retrieve horoscope readings for a specified zodiac sign through the AstroChalit API, helping users get astrological insights by sign.

Instructions

Execute horoscope AstroChalit API

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": {
      "signName": "<signName>"
    },
    "name": "get_horoscope"
  }
}

Input Schema

NameRequiredDescriptionDefault
signNameYesThe zodiac sign in lowercase

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

C2/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full behavioral burden, yet it discloses nothing about return format, whether results are cached or time-dependent, auth/API key needs, rate limits, or error behavior. "Execute...API" is the only hint, and it is too thin to be actionable.

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

Conciseness2/5

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

It is short, but that brevity is under-specification rather than economy: a single phrase that conveys no scope, no conditions, and no differentiation. Nothing is front-loaded because there is essentially no content to order.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no annotations and no output schema, the description is the only source of behavioral and return-value context, and it supplies neither. For a single-parameter call the schema is sufficient to invoke it, but an agent cannot predict what it will get back.

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 signName enum lists all twelve lowercase signs, so the parameter is fully documented structurally. The description adds no meaning beyond the schema, which places it at the baseline for high-coverage schemas.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The phrase "Execute horoscope AstroChalit API" essentially restates the tool name plus a vendor name; "Execute" describes the mechanics of the call, not the resource outcome. It does not say what a horoscope result contains (daily forecast, sign-based reading) or differentiate it from the many other astrology sibling tools.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of when another sibling (e.g. compatibility or divisional chart tools) would be preferred, and no prerequisites. An agent can only infer usage from the tool name and the single sign parameter.

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

Deploy Server

Other Tools