Skip to main content
Glama
Sign In

AstroLogics

by in.astrologics
OverviewDiscussionsAdmin

Pitra dosha check

check_pitra_dosha
Read-onlyIdempotent

Check a birth chart for the commonly cited Pitra dosha combinations: the Sun with Rahu or Ketu, Rahu or Ketu in the 9th house, the Sun with Saturn in the 9th house, and the 9th lord with Rahu or Ketu. Lists each combination found. Birth time is needed for the house-based checks.

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_pitra_dosha"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesBirth date, YYYY-MM-DD.
timeNoLocal birth time, HH:MM. Without it only the Sun-Rahu and Sun-Ketu checks are made.
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. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotent/non-destructive, so the safety profile is covered; the description adds the useful behavioral detail that results are listed per combination found and that omitting time silently narrows the check set. It does not describe authentication or failure behavior, which is minor for a stateless read.

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 purpose, then the specific combinations, then the prerequisite. No filler and nothing repeated unnecessarily.

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?

No output schema exists, and the description compensates by saying it lists each combination found and that partial input reduces coverage. The only gap is not stating the response when no dosha is detected, which an agent could infer but would prefer to be told.

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%, so every parameter already carries its own description, including the time-degradation rule and the language enum. The description repeats the time dependency but adds nothing new about date, latitude, or longitude, so baseline 3 applies.

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 and resource ("Check a birth chart for ... Pitra dosha combinations") and then enumerates the exact combinations tested, so an agent can distinguish it from check_manglik_dosha or check_kaal_sarp_dosha purely from the text.

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?

It gives clear context for use (birth-chart dosha screening) and a concrete prerequisite: birth time is needed for house-based checks. It stops short of naming an alternative tool or stating when not to use it, so it is not a 5.

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

All AstroLogics 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