Skip to main content
Glama
AstroChalit MCP Server

AstroChalit MCP Server

get_get_bala_details

Retrieves Vedic astrology bala (planetary strength) details for a specified bala type using birth date, time, latitude, and longitude.

Instructions

Execute get_bala_details 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>",
      "bala": "<bala>"
    },
    "name": "get_get_bala_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
dayYesDay of birth
balaYesThe bala type in the path
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, what it returns, error behavior, latency, or any prerequisite. For a 10-parameter computation endpoint this leaves an agent with zero behavioral signal.

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, but that brevity comes from under-specification rather than economy – the single phrase carries no usable information. Nothing is front-loaded because nothing substantive is said.

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?

A 10-parameter (9 required) astrological computation tool with no annotations and no output schema needs a description that explains the required 'bala' value, the expected input shape, and the result. This description supplies none of that and is wholly inadequate for the tool's complexity.

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 every field (birth date/time, latitude, longitude, timezone, and the 'bala' type) is already documented in the schema. The description adds no meaning beyond it, which is the baseline 3 case when the schema does the heavy lifting.

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?

"Execute get_bala_details AstroChalit API" only restates the tool name inside a generic wrapper; it never says what bala details are returned or what an AstroChalit calculation produces. It also gives no differentiation from the many sibling astrology endpoints (varshphal, dashakoot, divisional charts).

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 at all – nothing indicating what question this endpoint answers or which sibling to prefer for related calculations. The only implicit hint is the required 'bala' path parameter, which the description never explains.

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