Skip to main content
Glama

AstroNest — Vedic Astrology Readings

Reading of one life area

interpret_domain
Read-onlyIdempotent

Use this when the user asks what their chart says about one area of life (career, marriage, finance, health, property, children, education, travel, legal and others) and a reproducible verdict with its reasons and sources is wanted. Prefer it to get_forecast when no written narrative is needed. Deterministic reading of one life area: the verdict, the factors for and against it, timing windows, a cross-check of the verdict, and the classical texts it is grounded in. Every layer is declared as present, computed_empty, not_covered or failed, so nothing is silently missing. No language model is called: the same chart always gets the same reading. Cost: 5 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},"domain":"career"}

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>"
    },
    "name": "interpret_domain"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesLife area to read, e.g. career, marriage, finance or health.
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.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantial context beyond them: layer status semantics (present / computed_empty / not_covered / failed), no LLM in the loop, determinism, and a cost model of 5 credits per successful call with free sandbox keys. That is exactly the kind of operational detail annotations cannot carry.

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 trigger and the sibling comparison, then behavior, then cost — a sound ordering. It is slightly redundant, asserting determinism twice (the 'no language model is called' sentence and the standalone 'Deterministic:' line), which costs a bit of space.

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 nested two-parameter tool with an output schema, this covers trigger, alternative, return contents, partial-failure semantics, billing and a runnable example. An agent has everything needed to call it correctly and to set user expectations about cost.

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%, so the baseline is 3; the description earns above that by supplying a complete worked example arguments object showing the shape of the nested birthData plus domain. It doesn't add syntax or validation nuance beyond the schema, so it stops short of 5.

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 and resource — a deterministic reading of one life area — and enumerates the covered domains (career, marriage, finance, health, property, children, education, travel, legal). It explicitly contrasts itself with get_forecast, so an agent can place it against a sibling without opening the schema.

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?

Gives an explicit trigger ('when the user asks what their chart says about one area of life') plus a routing rule: prefer it over get_forecast when no written narrative is needed. It does not address the other plausibly-overlapping siblings such as get_life_reading, get_domain_timeline or get_guidance, which is the remaining gap.

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.