Skip to main content
Glama
AstroChalit MCP Server

AstroChalit MCP Server

get_varshphal_year_chart

Calculate a Varshphal solar return annual horoscope from birth details and a target year, returning the solar return moment and planetary positions.

Instructions

Calculate Varshphal Year Chart (Solar Return annual horoscope) based on birth details and yearInput, returning solar_return, momentTime, and planetary positions.

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

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

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

No annotations are provided, so the description carries the full behavioral burden, but it only names output fields (solar_return, momentTime, planetary positions) and does not state that the operation is read-only, side-effect-free, deterministic, or subject to input validation. It gives no error, permission, or rate-limit context.

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?

The definition is a single front-loaded sentence with no filler. It covers the calculation, the input basis, and the return fields without unnecessary repetition.

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 tool with no annotations and no output schema, the description provides the chart purpose and names the return fields, which is useful. However, it does not explain the returned fields or mention behavioral constraints, leaving clear gaps beyond input schema coverage.

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 the baseline is 3. The description refers to 'birth details and yearInput' but adds no syntax, format, or meaning beyond what the fully documented schema already provides.

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?

The description uses a specific verb and resource: 'Calculate Varshphal Year Chart' and clarifies it as a 'Solar Return annual horoscope'. This makes the annual-chart purpose clear, but it does not explicitly contrast with siblings such as get_varshphal_month_chart or get_varshphal_details.

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 does not state when to use this tool versus the many other Varshphal or divisional chart tools. Usage is only implied by the phrase 'Year Chart (Solar Return annual horoscope)', with no exclusions or alternative-selection guidance.

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