Skip to main content
Glama

AstroLogics

Kaal Sarp dosha check

check_kaal_sarp_dosha
Read-onlyIdempotent

Check Kaal Sarp dosha in a birth chart: whether all seven planets lie on one side of the Rahu-Ketu axis, and if so which of the twelve named types it is. Birth time is optional.

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": {
      "date": "<date>",
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "check_kaal_sarp_dosha"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesBirth date, YYYY-MM-DD.
timeNoLocal birth time, HH:MM. Optional.
languageNoSet to "hi" to add Hindi (Devanagari) names next to the English ones, for answering in Hindi.
latitudeYesBirth latitude in decimal degrees.
longitudeYesBirth longitude in decimal degrees.

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
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's job is to add computational context, which it does by disclosing the detection rule and the twelve-type classification result. The gap is that it never says what happens when time is omitted — presumably a degraded or Moon-based result — leaving the 'optional' claim unexplained.

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, no filler: the first carries the core definition and return scope, the second the one non-obvious input constraint. The most important information is front-loaded.

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 no output schema, the description does partial duty by revealing that the result is a boolean-style determination plus a type name among twelve. It is nearly complete for a low-complexity read-only check, but the consequence of omitting birth time remains unstated.

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 five parameters documented, including formats and the en/hi enum, so the baseline is 3. The description only restates the optionality of birth time, which the schema already declares, and adds no new meaning about date/location semantics.

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?

The description names a specific verb ('Check') and resource ('Kaal Sarp dosha in a birth chart') and then defines the exact criterion: whether all seven planets lie on one side of the Rahu-Ketu axis. It also scopes the output to one of twelve named types, which no sibling dosha tool claims, so an agent can distinguish this from check_manglik_dosha or check_pitra_dosha 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?

Usage is implied rather than stated: an agent infers this is the tool for a Kaal Sarp question. The one explicit practical hint is 'Birth time is optional,' but there is no when-to-use/when-not guidance relative to get_birth_chart or get_planet_positions, which would compute the underlying positions.

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