Skip to main content
Glama
AstroChalit MCP Server

AstroChalit MCP Server

get_rudraksha_suggestion

Calculate a Rudraksha recommendation using birth date, time, and location coordinates. Provide birth details to receive a Vedic astrology-based suggestion for selecting a Rudraksha.

Instructions

Execute rudraksha_suggestion 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": {
      "day": "<day>",
      "month": "<month>",
      "year": "<year>",
      "hour": "<hour>",
      "minute": "<minute>",
      "second": "<second>",
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "get_rudraksha_suggestion"
  }
}

Input Schema

NameRequiredDescriptionDefault
dayYesDay of birth
hourYesHour of birth (0-23)
yearYesYear of birth (e.g., 1990)
monthYesMonth of birth (1-12)
minuteYesMinute of birth (0-59)
secondYesSecond of birth (0-59)
latitudeYesLatitude of birth place
timezoneNoTimezone of birth place (e.g. Asia/Kolkata). Defaults to Asia/Kolkata
longitudeYesLongitude of birth place

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

C2.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it discloses nothing about what the call returns, whether it is a read-only computation, how errors surface, or whether there are rate or licensing constraints on the AstroChalit API. The phrase "Execute ... API" at least signals a remote API dependency, which is the only behavioral hint present.

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?

The definition is a single short sentence with no filler, but its brevity comes from under-specification rather than discipline — it spends its only words repeating the tool name and vendor name rather than front-loading useful information.

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?

For a nine-parameter tool with no annotations and no output schema, the definition is far too thin: an agent cannot tell what a rudraksha suggestion is, what form the answer takes, or why it would be chosen over the gemstone sibling. The well-documented input schema covers the parameters, but purpose and result remain unexplained.

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%, with each of the nine fields documented inline including ranges and the timezone default, so the baseline of 3 applies. The description adds no additional meaning about units, coordinate conventions, or how the timezone interacts with the birth time.

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 description reads "Execute rudraksha_suggestion AstroChalit API," which essentially restates the tool name with a generic verb. It never states that the tool produces a rudraksha bead recommendation from birth details, nor does it distinguish this from the sibling gemstone tool get_gemstone_suggestion. An agent can only guess the purpose from the name itself.

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 prerequisites, and no reference to the closely related get_gemstone_suggestion sibling. The only implied usage is that a caller supplies full birth data, which is evident from 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.

Deploy Server

Other Tools