Skip to main content
Glama

AstroNest — Vedic Astrology Readings

Written answer about what lies ahead

get_forecast
Read-only

Use this when the user asks an open question about what lies ahead in one area of life and wants a written answer. It takes tens of seconds; for a fast, structured verdict use interpret_domain. The interpret verdict for domain, voiced as a narrative answer to question by a language model grounded in the classical statements for the domain. Expect tens of seconds; set a client timeout of at least 90 s. Cost: 8 credits per call (only successful calls are charged; a sandbox key is free and returns a fixed sample). Voiced by a language model: allow up to 90 seconds. Example arguments: {"birthData":{"date":"1990-05-12","time":"14:35","timezone":"Asia/Kolkata","latitude":28.6139,"longitude":77.209},"domain":"career","question":"How will the next year unfold for my work?"}

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>",
      "domain": "<domain>",
      "question": "<question>"
    },
    "name": "get_forecast"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesLife area the question is about, e.g. career, marriage, finance or health.
questionYesThe question in plain language, e.g. "What does the next year hold for my career?"
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. Changed1 schema field changed
    • changedOutput schema / $defs / CorpusResolution / description
      Previous value: -"The weighed position of the classical corpus on this chart, as counts. Never source names on this surface."New value: +"How the classical evidence on this chart leans, as counts. Never source names on this surface."
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations: discloses non-trivial latency and a required client timeout of at least 90 s, a credit cost of 8 per call with only successful calls charged, and free sandbox keys returning fixed samples. These are exactly the operational facts an agent needs before committing to a slow, paid call, and none of them are recoverable from readOnlyHint/destructiveHint.

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?

Front-loaded and useful, but the latency warning is stated three times ('takes tens of seconds', 'Expect tens of seconds; set a client timeout of at least 90 s', 'allow up to 90 seconds'), which is redundant. The example arguments block is justified, but the repeated timeout phrasing costs space without adding information.

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?

For a 3-parameter nested-schema tool with an output schema and rich annotations, everything an agent needs is present: purpose, alternative, cost, timeout, and a worked example. Return values are correctly left to the output schema.

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 coverage is 100% and the enum plus birthData sub-schema are well documented, so the baseline is 3. The description adds value by clarifying that domain selects the grounding corpus and question is voiced verbatim into the narrative, plus a fully populated example argument set.

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 concrete deliverable: a narrative, LLM-voiced answer to an open question about one life area, grounded in the classical statements for that domain. It explicitly contrasts with the sibling interpret_domain, which returns a fast structured verdict, so an agent can route without opening either schema.

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?

Gives an explicit when-to-use condition (open-ended question, wants a written answer) and an explicit alternative (interpret_domain for a fast structured verdict). Latency and cost are also framed as selection criteria, not just trivia.

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.