Skip to main content
Glama

AstroNest — Vedic Astrology Readings

Guidance for the running daśā periods

get_guidance
Read-onlyIdempotent

Use this when the user asks how to conduct themselves in the period they are in: what to do and what to take care with, each with its classical reason. Guidance, not prediction. Plain-language guidance cards for each running daśā level (mahādaśā, antardaśā, …) at referenceDate (default: now). Cost: 3 credits 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_guidance"
  }
}

Input Schema

NameRequiredDescriptionDefault
birthDataYesThe person's birth data: date, local time (omit if unknown), IANA timezone, latitude and longitude.
referenceDateNoISO date or datetime. Defaults to now.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already cover read-only/idempotent/non-destructive, and the description still adds real behavioral facts not in them: 3 credits per call with only successful calls charged, a free sandbox key returning a fixed sample, and full determinism. That is exactly the cost/authorization/edge-case context an agent needs before spending credits.

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?

Front-loaded with the use case, then output shape, cost, determinism, and an example — a sensible priority order with short lines. The cost/sandbox line is slightly dense but each sentence carries information an agent needs before calling.

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?

An output schema exists, so return values need no explanation; the description covers the remaining agent-critical unknowns: what kind of content comes back, which daśā levels, the referenceDate default, cost, sandbox behavior, and determinism. Nothing needed to invoke it correctly is missing.

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%, so the baseline is 3; the description earns one extra point by including a fully-formed example argument that shows how the nested birthData object is assembled in practice (date, time, timezone, lat/long), which is the main place an agent could err.

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 outcome — plain-language guidance cards for each running daśā level (mahādaśā, antardaśā, …) at referenceDate — plus a sharp framing: 'Guidance, not prediction.' That framing implicitly separates it from get_forecast/get_dasha, but no sibling is named, so differentiation requires the agent to infer which existing daśā tool returns periods versus conduct advice.

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 clause gives a concrete trigger: the user asks how to conduct themselves in the period they are in, what to do and what to take care with. It provides a clear positive usage context but offers no explicit exclusions or a named alternative for when the agent instead needs raw period dates (get_dasha) or forecasts.

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.