Skip to main content
Glama
AstroChalit MCP Server

AstroChalit MCP Server

get_varshphal_planets

Calculate Varshphal planetary positions and details from birth data and a target year, returning solar return timing, moment time, and planet details for yearly astrological analysis.

Instructions

Calculate Varshphal planetary positions and details based on birth details and yearInput, returning solar_return, momentTime, and planetDetails.

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>",
      "yearInput": "<yearInput>"
    },
    "name": "get_varshphal_planets"
  }
}

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
yearInputYesTarget year (e.g. 2025)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

B3.2/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. It discloses that the tool is a calculation over birth data plus yearInput and enumerates three response keys, which implies a read-only computation, but it says nothing about ayanamsa/system choices, determinism, rate limits, or error conditions such as invalid coordinates.

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 the action and return fields up front and no filler. The trailing 'and details' is slightly vague, but nothing is wasted.

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?

Given ten parameters, nine of them required, no annotations, and no output schema, the definition is minimal but workable: required inputs are all documented in the schema and the three main return keys are named. It lacks any guidance on choosing yearInput versus birth year or on how to interpret the returned planetary data, which leaves real gaps for a 10-parameter 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 every parameter (including timezone default and latitude/longitude ranges) is documented inline, so the baseline is 3. The description only echoes 'birth details and yearInput' and adds no format, ordering, or constraint detail beyond the schema.

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 and resource: 'Calculate Varshphal planetary positions and details based on birth details and yearInput.' It also names the primary return fields (solar_return, momentTime, planetDetails). It does not distinguish this tool from siblings like get_varshphal_details or get_kp_planets, so it stops short of a 5.

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?

There is no explicit when-to-use guidance, no statement of when not to use it, and no named alternative. The agent must infer from the name and from the fact that birth details plus a target year are required that this is the Varshphal (annual chart) planetary-position tool.

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