Skip to main content
Glama

AstroNest — Vedic Astrology Readings

Relationship reading (non-marital)

get_relationship_reading
Read-onlyIdempotent

Use this when the user asks how two people get on in a bond other than marriage — business partners, siblings, a parent and child, or friends. Reads the bond the way the classical method reads it: the houses that govern this kind of bond and their lords in each chart, the natural significators, whose planets fall in whose governing houses, and whether that reach runs both ways, plus the running periods in each chart that engage the bond. A bond meter (strong tie, workable or strained) is computed by a stated convention and returned with every point it is built from; it is not a classical score, since the texts give no arithmetic for a business or sibling match. Deterministic: no language model is called. Both birth times are required. For marriage, use the compatibility tool. Cost: 8 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: {"type":"business","a":{"date":"1990-05-12","time":"14:35","timezone":"Asia/Kolkata","latitude":28.6139,"longitude":77.209,"name":"A"},"b":{"date":"1991-11-03","time":"06:10","timezone":"Asia/Kolkata","latitude":19.076,"longitude":72.8777,"name":"B"}}

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": {
      "type": "<type>",
      "a": "<a>",
      "b": "<b>"
    },
    "name": "get_relationship_reading"
  }
}

Input Schema

NameRequiredDescriptionDefault
aYesFirst person: birth data (time required) plus optional name.
bYesSecond person: birth data (time required) plus optional name.
typeYesThe bond. For marriage, call /v1/compatibility.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / a / type
      Added value: +"object"
    • addedInput schema / properties / b / type
      Added value: +"object"
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annnotations already declare readOnly/idempotent/non-destructive, and the description still adds substantial operational context: 8-credit cost, successful-calls-only billing, free sandbox sample, no LLM call, deterministic output. It also honestly discloses a non-obvious limitation — the bond meter is a computed convention, not a classical score — which an agent must know to avoid over-claiming authority for the reading.

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 trigger in the first sentence, then method, caveat, cost, determinism and example — a sensible priority order with little waste. It runs long, and 'Deterministic' is effectively stated twice (mid-paragraph and again as a standalone line), which is the only real redundancy.

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?

Given a rich nested schema, an output schema, and full annotation coverage, the description fills the remaining gaps an agent needs: what the reading actually analyzes (governing houses and lords, significators, house-to-house reach, running periods), the meaning of the composite score, cost model, and determinism. Nothing material for correct invocation 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 coverage is 100%, so baseline is 3; the description adds value with a fully worked example argument object that shows the expected shape of the nested a/b persons and the type value. One caveat: it states 'Both birth times are required', while the schema marks time as optional and says to omit it if unknown — a minor tension an agent may hit with partial data.

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 verb (reads the bond) and a precisely scoped resource (non-marital relationship between two people), enumerating the covered bond types: business, siblings, parent/child, friends. It also explicitly excludes marriage and names the sibling tool for that case, so an agent can discriminate it from get_compatibility 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?

Opens with an explicit trigger ('Use this when the user asks how two people get on in a bond other than marriage') and closes with the exclusion and its alternative ('For marriage, use the compatibility tool'). The type enum values are enumerated in prose, so the agent knows which bond categories route here.

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.