Skip to main content
Glama

AstroNest — Vedic Astrology Readings

Life-period timeline (planetary periods)

get_dasha
Read-onlyIdempotent

Use this when the user asks which planetary period (daśā) they are in, when it ends, or which periods are coming. The current periods include the running pratyantardaśā; send depth 'pratyantardasha' for the full timeline at that level. Cost: 1 credit per call (only successful calls are charged; a sandbox key is free and returns a fixed sample). Deterministic: the same input always gives the same answer. Example arguments: {"birthData":{"date":"1990-05-12","time":"14:35","timezone":"Asia/Kolkata","latitude":28.6139,"longitude":77.209}}

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": {
      "birthData": "<birthData>"
    },
    "name": "get_dasha"
  }
}

Input Schema

NameRequiredDescriptionDefault
depthNoTimeline depth. 'pratyantardasha' nests the pratyantardaśās under each antardaśā (about ten times larger). The current periods always include the running pratyantardaśā.antardasha
birthDataYesThe person's birth data: date, local time (omit if unknown), IANA timezone, latitude and longitude.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / depth
      Added value: +{
      +  "default": "antardasha",
      +  "description": "Timeline depth. 'pratyantardasha' nests the pratyantardaśās under each antardaśā (about ten times larger). The current periods always include the running pratyantardaśā.",
      +  "enum": [
      +    "antardasha",
      +    "pratyantardasha"
      +  ],
      +  "type": "string"
      +}
    • addedOutput schema / $defs / CurrentDasha / properties / pratyantardasha
      Added value: +{
      +  "description": "The running pratyantardaśā.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / $defs / CurrentDasha / properties / pratyantardashaEnd
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / $defs / DashaPeriod / properties / pratyantardashas
      Added value: +{
      +  "description": "On each antardaśā when depth is 'pratyantardasha'.",
      +  "items": {
      +    "$ref": "#/$defs/DashaPeriod"
      +  },
      +  "type": "array"
      +}
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, and closed-world, so the safety profile is covered. The description adds genuinely non-obvious operational facts: 1 credit per call with charges only on success, a free sandbox key returning a fixed sample, and determinism. It does not note pagination or response size despite 'about ten times larger' for pratyantardasha, but the cost/determinism disclosure is real value beyond the annotations.

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?

Usage trigger is front-loaded, followed by the depth instruction, then cost and determinism, then a worked example. Every line earns its place and there is no filler. The inline JSON example makes it slightly heavy but it is functional, not 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?

An output schema exists, so return values need not be explained, and the description covers trigger, depth control, cost model, and a full valid argument example. The only gap is relational: with a sibling like get_domain_timeline in the set, an agent lacks a rule for choosing between them.

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 the schema already documents depth, its enum values, and every birthData field including the 'omit time if unknown' caveat. The description's depth note largely restates the schema; the example arguments add concrete format value, but this is baseline territory rather than added semantic depth.

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?

The description names a specific resource (planetary period / daśā timeline) and the exact questions it answers: which period is running, when it ends, which are upcoming. That is far beyond restating the title. It does not, however, distinguish itself from close siblings such as get_domain_timeline or get_forecast, which an agent could plausibly reach for instead.

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

Usage Guidelines4/5

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

The opening sentence gives a concrete usage trigger in user-intent terms, and the depth line tells the agent exactly which argument value unlocks the deeper timeline. No exclusion or alternative-route guidance is offered (e.g. when to prefer get_domain_timeline), so it stops short of a 5.

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.