Skip to main content
Glama

Supastro

Cast the divisional charts (vargas)

get_divisional_charts
Read-onlyIdempotent

Calculates the divisional charts of a birth chart: Hora (D2), Drekkana (D3), Chaturthamsha (D4), Saptamsha (D7), Navamsa (D9), Dashamsha (D10), Dwadashamsha (D12), Shodashamsha (D16), Vimshamsha (D20), Chaturvimshamsha (D24), Saptavimshamsha (D27), Trimshamsha (D30), Khavedamsha (D40), Akshavedamsha (D45), Shashtiamsha (D60). For each it gives the chart's own Lagna, every planet's sign and house, its dignity there, and whether it is vargottama; the Shashtiamsha is given by planet, as each planet's portion with its classical name. Use it when someone asks for their D10, D7, D2 or another varga, or which planets are vargottama in it. Needs the birth date, time and place.

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_divisional_charts"
  }
}

Input Schema

NameRequiredDescriptionDefault
chartsNoOptional. Which divisional charts to calculate. Leave out for all of them.
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.9/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent and non-destructive, so the description's job is the payload — and it does that well: per-chart Lagna, planet sign and house, dignity, vargottama flag, plus the special per-planet treatment of Shashtiamsha. With no output schema, this return-value detail is genuinely load-bearing; only rate limits or failure modes are absent.

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 action and the trigger sentence, and the closing prerequisite is short. The 15-item varga list is bulky and largely duplicates the schema enum, but it does convey the full breadth of output in one glance.

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?

For a read-only computation tool with six well-documented parameters and no output schema, the description supplies the trigger, the inputs required and the shape of the results. An agent could call it correctly without further context; only the overlap with the dedicated navamsa sibling is left unresolved.

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%, including the varga enum and coordinate pairing rules, so the schema carries parameter meaning. The description only echoes the required birth date, time and place, adding nothing about the optional charts, latitude or longitude arguments beyond what is already documented.

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 ("Calculates the divisional charts of a birth chart") and enumerates every varga handled, so the scope is unmistakable. The one gap is the sibling get_navamsa_chart: the description claims D9 among its outputs without saying why an agent would pick this tool over that dedicated one.

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?

"Use it when someone asks for their D10, D7, D2 or another varga, or which planets are vargottama in it" gives a concrete trigger, and "Needs the birth date, time and place" states the prerequisite. It stops short of naming an alternative or a when-not condition, so it is clear context rather than full routing guidance.

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