Skip to main content
Glama
AstroChalit MCP Server

AstroChalit MCP Server

get_yogini_maha

Computes Yogini Maha Dasha periods using birth date, time, and optional coordinates or timezone to support Vedic astrology timing analysis.

Instructions

Execute yogini_maha 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>"
    },
    "name": "get_yogini_maha"
  }
}

Input Schema

NameRequiredDescriptionDefault
dayYesDay of birth (1-31)
hourYesHour of birth (0-23)
yearYesYear of birth (e.g. 1995)
monthYesMonth of birth (1-12)
minuteYesMinute of birth (0-59)
secondYesSecond of birth (0-59)
latitudeNoLatitude of birth place (optional)
timezoneNoTimezone (optional, default: Asia/Kolkata)
longitudeNoLongitude of birth place (optional)

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 disclosure burden, and it discloses nothing: no indication of whether the call is a read-only computation, whether defaults like the Asia/Kolkata timezone are applied silently, what the response contains, or how errors surface. The phrase 'Execute ... API' conveys no behavioral traits beyond the bare fact that a remote call occurs.

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?

The single short sentence contains no wasted words but is under-specified rather than concise; there is no front-loaded statement of purpose, inputs, or output to anchor the agent. Brevity here reflects missing content, not economy.

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 an astrological computation tool with six required date/time parameters, three optional location parameters, no output schema, and no annotations, the description should at minimum explain what the call returns. Instead it is silent on inputs, outputs, and the distinction from get_yogini_sub, leaving the agent unable to evaluate results.

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 all nine parameters (including the optional latitude/longitude/timezone) are documented in the schema itself, so the baseline of 3 applies. The description contributes no additional meaning such as units, precision expectations, or whether the optional location fields materially change the result.

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 reads 'Execute yogini_maha AstroChalit API', which essentially restates the tool name and adds only the vague verb 'Execute'. It never says what a yogini_maha dasha is, what period or result is produced, or how it differs from the closely named sibling get_yogini_sub.

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 information (e.g. that birth date/time and place are needed), and no mention of when to prefer get_yogini_sub or any dasha sibling. An agent must infer the selection criteria entirely from tool names.

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