Skip to main content
Glama

Supastro

Cast a Vedic birth chart

cast_birth_chart
Read-onlyIdempotent

Calculates a Vedic (sidereal, Lahiri) birth chart from a birth date, clock time and place: the rising sign (Lagna), and for each of the nine planets its sign, whole-sign house, degree, nakshatra and pada, plus the Moon's nakshatra. Use it when someone asks for their kundli, rising sign, Moon sign, nakshatra or planet placements. Returns calculated positions only, with no interpretation. The rising sign changes about every two hours, so an exact birth time matters.

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": {
      "birth_date": "<birth_date>",
      "birth_time": "<birth_time>",
      "birth_place": "<birth_place>"
    },
    "name": "cast_birth_chart"
  }
}

Input Schema

NameRequiredDescriptionDefault
latitudeNoOptional. Latitude of the birth place in decimal degrees, north positive. Give it only together with longitude, when the user supplied coordinates or the place could not be found by name.
longitudeNoOptional. Longitude of the birth place in decimal degrees, east positive. Give it only together with latitude.
birth_dateYesDate of birth as YYYY-MM-DD, for example 1990-01-15 for 15 January 1990. People write dates in different orders: day first in India and most countries, month first in the United States. Convert what the person wrote to YYYY-MM-DD yourself. If an all-number date could be read two ways, such as 05-06-1990, ask which number is the day before calling; never assume.
birth_timeYesLocal clock time of birth at the birth place, 24-hour HH:MM, for example 10:30, or 16:26 for 4:26 PM. If the person gave an hour from 1 to 12 without AM or PM, ask which before calling. Ask the user if the time is unknown; do not guess it.
birth_placeYesCity and country of birth, for example "Mumbai, India".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds value beyond them: the return is "calculated positions only, with no interpretation" (setting expectations that no prediction or advice comes back), and it flags the accuracy constraint that the Lagna shifts roughly every two hours, so a precise birth time is required.

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?

Four sentences, each doing distinct work: what is computed, when to invoke it, what comes back, and the accuracy caveat. The core purpose is front-loaded in the first clause, and nothing is repeated from the schema or annotations.

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?

With no output schema, the description carries the burden of explaining return content, and it does so precisely by listing the per-planet fields returned. For a read-only calculation tool whose annotations cover the safety profile, no information an agent needs to call it correctly is missing.

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, but the description contributes the *reason* the birth_time parameter is precision-critical (the rising sign changes about every two hours), reinforcing why the schema's guard against guessed times matters. It does not, however, add anything about the optional latitude/longitude pairing beyond what the schema already says.

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?

States a specific verb and resource ("Calculates a Vedic (sidereal, Lahiri) birth chart") and immediately enumerates the outputs: Lagna, and sign, whole-sign house, degree, nakshatra and pada for the nine planets, plus the Moon's nakshatra. That level of output detail lets an agent distinguish this from siblings like get_planet_positions or get_navamsa_chart without opening any schema.

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?

Gives concrete trigger phrases ("kundli, rising sign, Moon sign, nakshatra or planet placements"), which maps user intent directly onto this tool. It stops short of naming an alternative or stating when *not* to use it — e.g. when only a single planet placement or a divisional chart is wanted — so it is clear context without explicit 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