Skip to main content
Glama

Jyotish — Vedic astrology for AI agents

by io.github.entradox
OverviewDiscussionsAdmin

get_doshas

Dosha screen for birth data: Manglik standing under both conventions (Moon and Lagna), Kaal Sarp detection, Sade Sati phase, and extra classical yogas. Deterministic, no LLM. lang: en or hi (default en). Same compute path as POST /api/b2b/doshas.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
langNo
birth_dataYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / properties / birth_data / properties / place
      Removed value: -{
-  "description": "Birth place as a name (e.g. \"Jaipur\"). Resolved server-side through the same geocoder the bot uses, so an agent never has to guess coordinates. Supply EITHER place OR lat/lng/tz; if both are present, the explicit coordinates win.",
-  "type": "string"
-}
    • changedInput schema / properties / birth_data / properties / tz / description
      Previous value: -"UTC offset (e.g. 5.5) or IANA zone name (e.g. Asia/Kolkata). Required alongside lat/lng; ignored when `place` is used."New value: +"UTC offset (e.g. 5.5) or IANA zone name (e.g. Asia/Kolkata)."
    • changedInput schema / properties / birth_data / required
      Previous value: -[
-  "dob",
-  "tob"
-]New value: +[
+  "dob",
+  "tob",
+  "lat",
+  "lng",
+  "tz"
+]
  2. Changed3 schema fields changed
    • addedInput schema / properties / birth_data / properties / place
      Added value: +{
+  "description": "Birth place as a name (e.g. \"Jaipur\"). Resolved server-side through the same geocoder the bot uses, so an agent never has to guess coordinates. Supply EITHER place OR lat/lng/tz; if both are present, the explicit coordinates win.",
+  "type": "string"
+}
    • changedInput schema / properties / birth_data / properties / tz / description
      Previous value: -"UTC offset (e.g. 5.5) or IANA zone name (e.g. Asia/Kolkata)."New value: +"UTC offset (e.g. 5.5) or IANA zone name (e.g. Asia/Kolkata). Required alongside lat/lng; ignored when `place` is used."
    • changedInput schema / properties / birth_data / required
      Previous value: -[
-  "dob",
-  "tob",
-  "lat",
-  "lng",
-  "tz"
-]New value: +[
+  "dob",
+  "tob"
+]
  3. Added

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose two useful traits: the output is deterministic and no LLM is involved, plus parity with the REST endpoint. It does not state side effects, permissions, or whether the call is read-only, which matters less for a pure computation but is still unstated.

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?

Three tight sentences, front-loaded with what is computed, then determinism, then the lang parameter and endpoint parity. No filler.

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?

There is no output schema and no annotations, but the description effectively enumerates the return content (Manglik, Kaal Sarp, Sade Sati, yogas), which is what an agent needs to know. Missing only return shape/format details, which is a minor gap for a compute-only tool.

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 0%, so the description must compensate. It adds the only real semantic beyond the schema: 'lang: en or hi (default en)' — the default value is not in the schema. The birth_data fields (dob, tob, lat, lng, tz) are documented in the schema, so the description's contribution is limited but non-zero.

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

Purpose4/5

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

States a specific verb+resource (dosha screen for birth data) and enumerates the exact computations returned: Manglik under both conventions, Kaal Sarp, Sade Sati, and classical yogas. This is clearly distinguishable from siblings like get_dasha or get_chart_facts, though it never names a sibling explicitly.

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?

No when-to-use guidance, no conditions selecting this over get_chart_facts or get_dasha, and no exclusions. The 'Same compute path as POST /api/b2b/doshas' line is a routing/parity note, not usage guidance.

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

All Jyotish — Vedic astrology for AI agents 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