Skip to main content
Glama
AstroChalit MCP Server

AstroChalit MCP Server

get_sarvashtakvarga

Calculate Sarvashtak Varga totals across all zodiac signs and planets from birth date, time, and location. Use it to assess cumulative Ashtakavarga strength in a Vedic chart.

Instructions

Calculate Sarvashtak Varga (cumulative Ashtakvarga points across all zodiac signs and planets) 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_sarvashtakvarga"
  }
}

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden. 'Calculate' does imply a deterministic read-only computation, but the description says nothing about output shape, whether a timezone is required or defaulted, or precision requirements for birth time — all material for an astrological computation whose results shift with minutes of birth time.

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?

A single front-loaded sentence with no filler, and the parenthetical definition sits in the right place. It is appropriately short, though it is short partly because it omits information an agent would want.

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 nine-parameter computation with no annotations and no output schema, the description is thin: it never characterizes the return value or explains why precise birth time and coordinates matter. The complete schema metadata prevents this from being inadequate, but the description itself leaves real gaps.

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%, with every one of the nine parameters individually documented including ranges and the timezone default, so the schema does the heavy lifting. The description adds only 'based on birth details' and contributes no extra meaning such as which inputs dominate result accuracy.

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 ('Calculate') and resource ('Sarvashtak Varga'), and the parenthetical gloss 'cumulative Ashtakvarga points across all zodiac signs and planets' meaningfully defines the term for an agent unfamiliar with Jyotish vocabulary. It implicitly separates it from get_bhinnaashtakvarga (the per-planet, non-cumulative variant) but never names that sibling explicitly.

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?

No when-to-use or when-not-to-use guidance, no prerequisites, and no routing to alternatives such as get_bhinnaashtakvarga or the divisional chart tools. The only hint at usage is the vague 'based on birth details' phrase.

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