Skip to main content
Glama
AstroChalit MCP Server

AstroChalit MCP Server

get_jamini

Calculates Jamini astrology chart data from birth date, time, and coordinates via the AstroChalit API, enabling birth-chart analysis.

Instructions

Execute jamini 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_jamini"
  }
}

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?

With no annotations, the description carries the full burden and discharges none of it: nothing about what a successful response contains, whether the call is read-only, cost/rate limits of the upstream AstroChalit API, or what timezone defaulting does. "Execute ... API" conveys no behavioral trait at all.

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 a single short sentence with no filler, but the brevity comes from under-specification rather than economy; nothing is front-loaded because nothing informative 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?

For a 9-parameter, 8-required tool with no annotations and no output schema, the definition leaves the agent without any idea of the return shape or scope. This is well below what the tool's complexity demands.

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% across all 9 parameters (birth date/time, latitude, longitude, optional timezone defaulting to Asia/Kolkata), so the schema already explains each field. The description adds no extra meaning, which lands at the baseline 3 for high coverage.

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 jamini AstroChalit API" essentially restates the tool name (get_jamini) and names an upstream API, without saying what the call actually produces (a Jaimini/Chara-karaka chart? dashas? a full API payload?). It gives no distinguishing detail against the many other astrological sibling tools, so an agent cannot tell what this one returns that get_char_maha_dasha or get_divisional_chart_d9 does not.

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 prerequisites, and no mention of any alternative among the ~30 astrology siblings. The agent is left to infer that this is the general-purpose Jaimini request endpoint from the name alone.

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