Skip to main content
Glama

Supastro

Find the twelve Arudha padas

get_arudha_padas
Read-onlyIdempotent

Calculates all twelve Arudha padas of a birth chart, from the Arudha Lagna (AL) through the Darapada (A7) to the Upapada Lagna (UL): each pada's sign, its house from the Lagna and from the Arudha Lagna, and the planets in it. Use it when someone asks for their Arudha Lagna, Darapada, A10 or another pada. 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_arudha_padas"
  }
}

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/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 closed-world scope, so the safety profile is covered. The description goes beyond them by disclosing what the computation actually yields (signs, house positions from two reference points, occupying planets), which matters because there is no output schema. It does not address edge cases such as unknown birth time, though the schema handles those.

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?

Two sentences, both fully loaded: the first defines scope and enumerates the returned fields, the second gives the trigger and required inputs. Nothing is repeated and the substance is front-loaded.

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?

With no output schema, the description correctly carries the burden of describing return contents, and it does so. Inputs and triggering questions are covered by the description plus a fully documented schema. The only gap is the absence of any note on how this relates to sibling chart tools such as cast_birth_chart or get_special_lagnas.

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 the parameter descriptions are unusually rich, covering date ambiguity, AM/PM, and the latitude/longitude pairing rule. The description only restates that birth date, time and place are needed, adding no meaning beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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?

States a specific verb and resource ('Calculates all twelve Arudha padas of a birth chart') and enumerates the actual outputs: each pada's sign, its house from the Lagna and from the Arudha Lagna, and the planets in it. Naming AL, A7/Darapada and UL anchors the concept precisely. It stops short of distinguishing itself from the sibling get_special_lagnas, which could plausibly overlap in the agent's mind.

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 an explicit trigger ('Use it when someone asks for their Arudha Lagna, Darapada, A10 or another pada') and states the prerequisites (birth date, time, place). There are no exclusions or named alternatives for cases like a general special-lagna request, so it is clear context rather than full when/when-not 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