Skip to main content
Glama

Supastro

Find the special lagnas

get_special_lagnas
Read-onlyIdempotent

Calculates the special lagnas of a birth chart: Hora Lagna, Ghati Lagna, Bhava Lagna, Pranapada Lagna, Indu Lagna, Sree Lagna, Varnada Lagna, Karakamsa, Surya Lagna and Chandra Lagna. For each it gives the sign, the degree where one is defined, the house from the birth-chart Lagna, how it is found, and for the time-driven ones how many minutes of birth-time error would move it. Use it when someone asks for one of these lagnas by name. 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_special_lagnas"
  }
}

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.2/5.0
Behavior4/5

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

The annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so safety is covered. The description adds what the annotations cannot: the per-lagna payload (sign, degree where defined, house from the birth-chart Lagna, derivation method, and minutes of birth-time error for time-driven lagnas). It does not discuss cost or performance, but nothing here implies mutation or side effects.

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 verb and the full inventory of lagnas, then a compact statement of outputs and a usage sentence. The ten-name enumeration is long but earns its place by enabling name matching; nothing is redundant, though the sentence structure is dense rather than cleanly segmented.

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 return-value burden and does so precisely, including the nuanced qualifier "the degree where one is defined" for lagnas that lack a degree. Required inputs are stated and the schema handles coercions, so 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.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the schema itself carries detailed guidance on date-format ambiguity, AM/PM handling, and when to supply latitude/longitude. The description only restates the three required inputs ("Needs the birth date, time and place") and adds no meaning beyond the schema, so the baseline of 3 applies.

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 ("Calculates") and an enumerable resource (the ten named lagnas), so the agent knows exactly what comes back: Hora Lagna, Ghati Lagna, Bhava Lagna, Pranapada Lagna, Indu Lagna, Sree Lagna, Varnada Lagna, Karakamsa, Surya Lagna, Chandra Lagna. The naming makes it trivially separable from siblings like get_arudha_padas or get_jaimini_karakas.

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 one of these lagnas by name" gives a concrete trigger tied to the enumerated list, which is more than most definitions offer. It does not cross-reference a near alternative such as check_birth_time_sensitivity, even though it mentions birth-time error margins, so there is a small residual ambiguity for a user asking about time sensitivity.

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