Skip to main content
Glama

Cosmic Chemistry

Navamsa (D9) or dashamsha (D10) chart

divisional_chart
Read-onlyIdempotent

Use this when someone asks for their navamsa (D9) chart, read for marriage and inner strength, or their dashamsha (D10) chart, read for career ("my navamsa chart", "D9 chart", "Venus in my navamsa", "D10 career chart", "my ishta devata"). Set "chart" to d9 or d10. Returns the rising sign and every planet with its sign and house in that chart; the D9 adds the ishta and palana deities read from the karakamsha, the D10 the deity of each planet’s part. Needs birth date, time and town: the D9 rising sign moves on about every 13 minutes of birth time, the D10’s about every 12. Future dates to 2100 work too.

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>",
      "chart": "<chart>"
    },
    "name": "divisional_chart"
  }
}

Input Schema

NameRequiredDescriptionDefault
chartYesd9 for the navamsa, d10 for the dashamsha (career).
birth_dateYesDate of birth, YYYY-MM-DD, e.g. 1993-03-17.
birth_timeYesLocal clock time of birth, 24-hour HH:MM, e.g. 13:35. As exact as possible (from a birth certificate).
birth_placeYesTown or city of birth, with region or country if known, e.g. "Chicago, Illinois, US" or "Pune, India".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuinely new behavior: sensitivity of the rising sign to birth time (~13 min for D9, ~12 min for D10), that data to 2100 is supported, and extra D9/D10-specific outputs (ishta/palana deities, per-planet deity).

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?

Front-loaded with the use case and example phrasing, then the chart setting, return contents, and birth-data requirement in a logical order. It is one dense block rather than broken into sections, but no sentence is filler.

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?

For a four-required-param read-only lookup with no output schema, the description covers inputs, the enum choice, what comes back (rising sign, planet signs/houses, deities), and the precision constraint. An agent has everything needed to call it 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. The description still earns extra credit by explaining why birth_time must be exact (rising sign shifts every ~12–13 minutes) and by mapping each chart value to its interpretive purpose, which the enum alone does not state.

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?

Names the specific resource (navamsa D9 / dashamsha D10 divisional charts), says what each is read for (marriage/inner strength vs career), and example queries pin down the exact scope. An agent can distinguish this from vedic_birth_chart or chara_karakas without opening the 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 ("my navamsa chart", "D10 career chart", "my ishta devata") and ties the chart value to the ask, which is clear when-to-use guidance. It omits an explicit "not for X, use sibling Y instead" exclusion, so it stops short of routing against alternatives.

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