Skip to main content
Glama

Supastro

Calculate the Ashtakavarga points

get_ashtakavarga
Read-onlyIdempotent

Calculates the Ashtakavarga of a birth chart: the Sarvashtakavarga points of each of the twelve houses with the classical reading of that score, and each planet's own points (Bhinnashtakavarga) in every sign. Use it when someone asks for their Ashtakavarga, their Sarvashtakavarga or SAV score for a house, or a planet's points (bindus) in a sign. Returns the computed points and the classical scale they are read on.

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

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?

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully carried elsewhere. The description adds that it returns both the computed points and the classical scale they are read on, which tells the agent what kind of answer to expect. It omits any caveat about birth-time accuracy affecting results, which is the main remaining gap.

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: the first defines the computation and its two components, the second gives usage triggers, and a short closing sentence covers the return. Front-loaded, no redundancy, nothing to trim.

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 five-parameter computational tool with no output schema, the description is nearly complete: it names the outputs and the classic scale so the agent need not guess at return values. The only thing missing is any note that unstable birth data degrades the result, which would help the agent set expectations.

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%, so every parameter (including the optional latitude/longitude pair and the date/time ambiguity rules) is already documented in the schema. The description adds no parameter-level meaning beyond that, so the baseline 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 and resource ("Calculates the Ashtakavarga of a birth chart") and enumerates the two computed outputs, Sarvashtakavarga house points and Bhinnashtakavarga per-sign points. No sibling tool in the catalog computes Ashtakavarga, and the description makes the distinction clear without needing the schema opened.

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 explicit trigger phrasings: when someone asks for their Ashtakavarga, their Sarvashtakavarga or SAV score for a house, or a planet's bindus in a sign. That maps user intent to the tool well. It does not state when *not* to use it or name a neighboring alternative, so it stops short of the top band.

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