Skip to main content
Glama
AstroChalit MCP Server

AstroChalit MCP Server

get_bhinnaashtakvarga

Calculate a planet's Bhinnashtak Varga score table across all 12 zodiac signs from birth date, time, and location to assess its strength in a Vedic chart.

Instructions

Calculate Bhinnashtak Varga (individual planetary score table across all 12 zodiac signs) for a specified planet based on birth details.

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": {
      "day": "<day>",
      "month": "<month>",
      "year": "<year>",
      "hour": "<hour>",
      "minute": "<minute>",
      "second": "<second>",
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "get_bhinnaashtakvarga"
  }
}

Input Schema

NameRequiredDescriptionDefault
dayYesDay of birth
hourYesHour of birth (0-23)
yearYesYear of birth (e.g., 1990)
monthYesMonth of birth (1-12)
minuteYesMinute of birth (0-59)
secondYesSecond of birth (0-59)
latitudeYesLatitude of birth place
timezoneNoTimezone of birth place (e.g. Asia/Kolkata). Defaults to Asia/Kolkata
longitudeYesLongitude of birth place
planetInputNoPlanet name to calculate Bhinna Ashtakvarga points for (Sun, Moon, Mars, Mercury, Jupiter, Venus, Saturn)Sun

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden, but it does disclose the input basis (birth details) and the shape of the result (a score table spanning 12 signs), which is meaningful with no output schema. It does not confirm the operation is a side-effect-free computation, nor does it mention the sidereal/ayanamsa assumption or timezone defaulting behavior.

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?

A single well-formed sentence that front-loads the verb and resource and closes with the two things that matter: the subject planet and the birth-data dependency. No filler, no repetition of schema fields.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 10-parameter computational tool with no annotations and no output schema, it covers the essentials: what is computed, from what inputs, and roughly what comes back. It leaves open behavioral details an agent would want — timezone fallback, which zodiac/ayanamsa system, and why only the seven classical planets are selectable — so it is adequate rather than complete.

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 each of the 10 parameters is individually documented with ranges and the planet enum, so the baseline of 3 applies. The description only reiterates that one parameter selects the planet and the rest are birth data, adding no format or syntax detail beyond the schema.

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 (Calculate) plus a precisely named, obscure resource, and glosses the term inline as an 'individual planetary score table across all 12 zodiac signs'. It also scopes it to a single planet, so an agent knows exactly what this produces versus the divisional-chart or dasha siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description is purely definitional. It never says when to reach for Bhinnashtak Varga instead of a divisional chart, a bala/dasha tool, or a combined ashtakavarga-style result, and it lists no prerequisites beyond 'birth details'.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools