Skip to main content
Glama

Cosmic Chemistry

What a mahadasha means

mahadasha_meaning
Read-onlyIdempotent

Use this when someone asks what a mahadasha or antardasha means in Vedic astrology in general, or how long one lasts, without asking for their own dates: "what does Rahu mahadasha mean", "Saturn mahadasha effects", "Jupiter mahadasha Venus antardasha", "how long is Ketu dasha". Returns the length of the period, what the planet stands for, what its years tend to bring in daily life, when they tend to work and when they strain, every antardasha in order with its length, and for an antardasha asked about, its note. For the person’s own dates use current_dasha. Read a period by where the planet sits in the chart, never as good or bad in itself; no fear.

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": {
      "planet": "<planet>"
    },
    "name": "mahadasha_meaning"
  }
}

Input Schema

NameRequiredDescriptionDefault
planetYesThe mahadasha lord.
antardashaNoOptional: the antardasha lord inside it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, non-destructive, closed-world), so the description focuses on substantive behavior: it itemizes the return contents (period length, planetary significations, effects, antardasha list with lengths and notes) and gives an interpretive framing rule ('read a period by where the planet sits in the chart, never as good or bad in itself; no fear'). It does not mention output format structure or error behavior, but the added context is well 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?

The trigger conditions and example queries are front-loaded, and every clause carries information (use cases, return contents, alternative tool, interpretive rule). It is dense and somewhat long, especially the enumerative middle, but no sentence is pure filler.

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

Completeness5/5

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

There is no output schema, and the description compensates by enumerating exactly what comes back (length, planetary meaning, effects, timing of support vs strain, ordered antardashas with lengths, and an antardasha note). Combined with 100% schema coverage, an agent has everything needed to select and call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% with enums for both parameters, so the baseline is 3. The description adds meaning by explaining the relationship between the two: antardasha is a sub-period inside the mahadasha, and supplying it changes the output to include that antardasha's note.

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

Purpose5/5

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

States a specific verb+resource: it explains what a mahadasha or antardasha MEANS in Vedic astrology, and it enumerates concrete query shapes it answers. It also distinguishes itself from the sibling current_dasha by scoping itself to general meaning rather than the user's own dates.

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

Usage Guidelines5/5

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

Explicitly gives the when ('what does Rahu mahadasha mean', 'how long is Ketu dasha') and the when-not ('without asking for their own dates'), plus the named alternative: 'For the person's own dates use current_dasha.' Nothing is left to inference.

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