Skip to main content
Glama
AstroChalit MCP Server

AstroChalit MCP Server

get_varshphal_harsha_bala

Computes planetary Harsha Bala strengths for a Varshphal chart using birth date, time, location coordinates, and timezone.

Instructions

Execute varshphal_harsha_bala AstroChalit API

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

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

D1.9/5.0
Behavior1/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it discloses nothing about whether the call is read-only or mutating, what it computes, what the response contains, or whether any defaults (like the timezone fallback) are applied. The single sentence is functionally opaque.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short with no padding, but that brevity comes from under-specification rather than economy: one jargon sentence with no front-loaded statement of purpose, output, or scope. Length is not the problem; the absence of any substantive content is.

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

Completeness1/5

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

For a tool requiring 8 of 9 parameters with no annotations and no output schema, the description should explain what is being calculated and roughly what comes back. It says nothing, leaving the agent unable to judge correctness of use beyond the schema's field-level hints.

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% — every one of the 9 parameters has a documented meaning and range — so the schema already does all the semantic work. The description adds no extra meaning such as whether coordinates are the birth place or event place, but the baseline of 3 applies when the schema is self-sufficient.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description only restates the tool name plus the phrase 'AstroChalit API'; it never says what harsha_bala computes (a Vedic planetary strength measure within an annual/varshphal chart) or what the caller receives. An agent seeing siblings like get_get_bala_details and get_varshphal_details has no basis from this text for telling them apart.

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 when-to-use guidance, no prerequisite (e.g., that it requires a full birth date/time and coordinates), and no mention of when a different varshphal tool is preferable. 'Execute ... API' is a mechanical label, not usage direction.

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