Skip to main content
Glama

AstroLogics

Antardasha and pratyantardasha periods

get_antardasha
Read-onlyIdempotent

Get the running Vimshottari mahadasha, antardasha (bhukti) and pratyantardasha with their dates, the next ones, and the antardasha sequence. Uses a saved chart from the signed-in user's AstroLogics account or given birth details, with the chart features of the user's plan.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_antardasha"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoBirth date, YYYY-MM-DD (when not using a saved chart).
timeNoLocal birth time, HH:MM (when not using a saved chart).
chartNoA saved chart's id or name from list_my_charts. Or give the birth details below instead.
languageNoSet to "hi" to add Hindi (Devanagari) names next to the English ones, for answering in Hindi.
latitudeNoBirth latitude in decimal degrees (when not using a saved chart).
longitudeNoBirth longitude in decimal degrees (when not using a saved chart).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real context beyond that: the data can come from the signed-in user's saved AstroLogics chart or from supplied birth details, and results are bounded by the user's plan features. It does not say what happens when neither a chart nor birth details are provided.

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

Conciseness4/5

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

One tight sentence with the resource list front-loaded and the input-source conditions trailing, so the agent reads the what before the how. Every clause carries information; nothing is padding.

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

Completeness4/5

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

For a six-parameter, zero-required read tool with no output schema, the description covers both what is returned (period names, dates, upcoming periods, sequence) and how the chart is sourced. The one omission is the mutual-exclusivity/precedence rule when both a chart id and birth details are supplied, or neither.

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 each property already documents its own role, including the 'when not using a saved chart' qualifiers. The description reinforces the chart-vs-birth-details split and the purpose of the language toggle implicitly, but adds no format or constraint detail beyond the schema. Baseline 3 is appropriate.

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

Purpose4/5

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

States a specific verb and resource set: the running Vimshottari mahadasha, antardasha (bhukti) and pratyantardasha with dates, plus upcoming periods and the antardasha sequence. It also gives the synonym 'bhukti', which helps matching. It does not, however, distinguish itself from the sibling get_vimshottari_dasha, which an agent could easily confuse it with.

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

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when the tool applies by describing the two input modes (saved chart vs. supplied birth details), which is genuine routing guidance for the caller. But it never states when to pick this over get_vimshottari_dasha or get_my_chart, and no exclusions are given. Usage is inferable rather than explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources