Skip to main content
Glama

Supastro

Cast the Navamsa (D9) chart

get_navamsa_chart
Read-onlyIdempotent

Calculates the Navamsa (D9), the ninth-division chart, for a birth: the Navamsa rising sign, each planet's Navamsa sign and its house counted from the Navamsa rising sign, and which planets are vargottama (in the same sign in the birth chart and the Navamsa). Use it when someone asks for their Navamsa or D9 chart, a planet's Navamsa sign, or whether a planet is vargottama. Returns calculated placements only. The Navamsa rising sign changes about every 13 minutes, 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": "get_navamsa_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

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety and determinism profile is fully covered without description help. The description does add two pieces of genuine behavioral context: 'Returns calculated placements only' (no interpretation layer) and the warning that the Navamsa rising sign changes roughly every 13 minutes, making birth-time exactness critical. What it does not address is whether output is formatted as text or structured, and there is no output schema to fall back on.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences arranged logically: what is computed, when to call it, what is returned, then the precision caveat. Nothing is padded and the key output list is front-loaded. Minor redundancy in glossing 'ninth-division chart' alongside 'D9', but it aids rather than burdens comprehension.

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 full return-value burden and discharges it by naming each returned element, including the vargottama flag. Combined with annotations covering safety and the required-input caveat about birth time, an agent has everything needed to decide to call it and to expect the right shape of result.

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%, and those descriptions are unusually thorough (date-order disambiguation, AM/PM clarification, when to supply coordinates), so the schema carries the parameter burden and the baseline is 3. The description adds only one indirect signal — that exact birth time matters because the rising sign shifts every ~13 minutes — which reinforces why birth_time is required and non-guessable. It never discusses latitude/longitude or birth_place, so it adds little beyond the schema.

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 names a specific verb ('Calculates') and a specific resource ('the Navamsa (D9), the ninth-division chart'), then enumerates exactly what is produced: the Navamsa rising sign, each planet's Navamsa sign and house from that rising sign, and vargottama status. That is far more specific than a title restatement. It stops short of 5 because it never distinguishes itself from the sibling tool that likely bundles divisional charts (get_divisional_charts), leaving a small routing ambiguity for an agent.

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 concrete triggering requests: 'when someone asks for their Navamsa or D9 chart, a planet's Navamsa sign, or whether a planet is vargottama.' This is clear context for use. It offers no explicit exclusions or named alternatives, so an agent facing 'show me all my divisional charts' gets no instruction on whether to call this or the divisional-charts sibling.

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