Skip to main content
Glama

AstroLogics

Vedic birth chart

get_birth_chart
Read-onlyIdempotent

Calculate a sidereal (Lahiri) Vedic birth chart: the ascendant, the nine grahas with sign, degree, nakshatra and house, and the navamsa, dashamsa and hora ascendants. Requires birth date and coordinates. Birth time improves accuracy and defaults to 12:00 when unknown.

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": "get_birth_chart"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesBirth date, YYYY-MM-DD.
timeNoLocal birth time at the birth place, HH:MM. Defaults to 12:00 if unknown.
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.
place_nameNoOptional place name as the user gave it, used only to prefill the details link.

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.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description contributes beyond that by disclosing the ayanamsa (Lahiri sidereal), the fallback behavior for missing birth time, and the specific output composition. It does not state whether the computed chart is persisted (versus needing save_chart), which is the one behavioral trait an agent would still want.

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 sentences, each earning its place: what is computed, what inputs are mandatory, and how the optional time behaves. Front-loaded with the core definition and no filler or restatement of the title.

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

Completeness5/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 the description compensates by naming every returned component (ascendant, nine grahas with sign/degree/nakshatra/house, and the three divisional ascendants). With 100% schema coverage, annotations covering the safety profile, and no nested objects, an agent has everything needed to invoke this correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3 and the schema carries most parameter detail. The description still adds meaning: it explains why 'time' matters (it improves accuracy, not just an accepted format) and ties date/coordinates to the calculation itself. It adds nothing for language or place_name, but those are self-documenting.

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?

The description opens with a specific verb and resource ('Calculate a sidereal (Lahiri) Vedic birth chart') and enumerates the exact outputs: ascendant, nine grahas with sign/degree/nakshatra/house, plus navamsa, dashamsa and hora ascendants. That enumeration distinguishes it from narrower siblings in effect, but it never names an alternative tool (e.g. get_divisional_chart or get_planet_positions), so sibling differentiation is left implicit.

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?

'Requires birth date and coordinates' plus the note that birth time is optional and defaults to 12:00 gives an agent clear preconditions for calling. What is missing is any explicit routing guidance — no statement of when to prefer get_my_chart, get_divisional_chart, or save_chart over this, and no exclusions.

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