Skip to main content
Glama

Supastro

Rank the planets by strength (Shadbala)

get_planet_strength
Read-onlyIdempotent

Calculates how strong each planet is in a birth chart by classical Shadbala: each planet's strength in rupas against the minimum the texts require, its rank from strongest to weakest, and its dignity, combustion, retrogression, vargottama status and the planets joining or aspecting it. Use it when someone asks which planet is strongest or weakest in their chart, for their Shadbala, or whether a named planet is strong. Returns the computed strengths with the reason behind each rating.

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

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

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds real value beyond that by disclosing what the output contains and that each rating comes with 'the reason behind each rating' — an explanatory contract an agent could not infer from the annotations. No permission, latency, or failure-mode notes, but none are notably needed for a pure computation.

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?

Two sentences, front-loaded with the computation before the use case. The middle clause is a dense list of seven output components, which is justified by the absence of an output schema, though it reads as a run-on. No filler sentences.

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 must describe return values and it does — strengths, rank, dignity, and per-rating reasoning. Input edge cases (ambiguous dates, missing birth time) are fully handled in the schema. It does not explain how to interpret a strength verdict (e.g., what counts as weak), a small remaining gap for a domain-specific ranking tool.

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 schema itself already spells out date formats, AM/PM disambiguation, and when to use latitude/longitude. The description says nothing about any parameter, adding 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 a specific resource ('how strong each planet is in a birth chart by classical Shadbala'), then enumerates the exact components produced: rupas vs. textual minimum, rank, dignity, combustion, retrogression, vargottama, conjunctions and aspects. This clearly separates it from sibling tools like get_planet_positions (positions) and get_daily_moon_strength (a single planet, daily).

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?

Explicit trigger conditions are given: 'which planet is strongest or weakest', 'for their Shadbala', or 'whether a named planet is strong'. That is clear when-to-use guidance with concrete user phrasings. It stops short of when-not-to-use or naming an alternative (e.g., get_planet_positions for raw degrees), so it falls short of a 5.

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