Skip to main content
Glama
AstroChalit MCP Server

AstroChalit MCP Server

get_yogini_sub

Calculate Yogini sub-periods (sub-dashas) from birth date, time, and optional location using the AstroChalit API.

Instructions

Execute yogini_sub 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_sub"
  }
}

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

C2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden, and it discloses almost nothing: it does not say whether the call is read-only, whether it performs a remote API request, what latency or auth constraints apply, or what the response contains. Only the word 'API' hints that this is a backend call.

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

Conciseness3/5

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

One short sentence with no wasted words, but the brevity comes from under-specification rather than tight editing. Nothing is front-loaded because there is no substantive content to order.

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?

With 9 parameters, 6 of them required, no annotations, and no output schema, the description should explain the required birth date/time inputs and expected result. It supplies none of that, leaving the tool effectively opaque beyond its schema.

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% with per-parameter descriptions, ranges, and a stated timezone default, so the input contract is fully documented without the description's help. The description adds no meaning beyond that schema, so the baseline 3 is the right ceiling.

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 is a bare restatement of the tool name plus an endpoint label: 'Execute yogini_sub AstroChalit API'. It says nothing about what yogini_sub actually computes, and it gives no signal to distinguish it from the sibling get_yogini_maha, so an agent cannot choose between the two.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/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 or birth-data requirement, and no named alternative. The only cue is the verb 'Execute', which carries no selection information.

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