Skip to main content
Glama

Supastro

Read one area of life from every chart layer

read_life_area
Read-onlyIdempotent

Calculates, in one answer, every layer of a birth chart that a question about one area of life rests on: career, money, marriage or relationship, children, property and home, education, spiritual path, the chart as a whole, or timing. It returns the birth chart with each planet's degree, nakshatra, dignity, retrogression and combustion; the area's houses with their lords, occupants and aspects; Ashtakavarga, Shadbala and Vimshopaka strength; the natural and Jaimini karakas; the Navamsa, the area's own divisional chart and each planet's Shashtiamsha (D60) portion; Bhava Chalit; the twelve Arudha padas including the Darapada (A7) and the Upapada; every special lagna; the yogas and doshas with their status; the four running dasha levels with dates and the periods ahead; and today's transits from the Lagna and the Moon. Use it when someone asks a real question about their life, such as how their career or marriage looks, when something may happen, or what their chart says overall. Needs the birth date, time and place.

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": {
      "birth_date": "<birth_date>",
      "birth_time": "<birth_time>",
      "birth_place": "<birth_place>",
      "area": "<area>"
    },
    "name": "read_life_area"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaYesThe area of life the question is about. Use general for a question about the chart as a whole, and timing for a question that is mainly about when.
latitudeNoOptional. Latitude of the birth place in decimal degrees, north positive. Give it only together with longitude, when the user supplied coordinates or the place could not be found by name.
longitudeNoOptional. Longitude of the birth place in decimal degrees, east positive. Give it only together with latitude.
birth_dateYesDate of birth as YYYY-MM-DD, for example 1990-01-15 for 15 January 1990. People write dates in different orders: day first in India and most countries, month first in the United States. Convert what the person wrote to YYYY-MM-DD yourself. If an all-number date could be read two ways, such as 05-06-1990, ask which number is the day before calling; never assume.
birth_timeYesLocal clock time of birth at the birth place, 24-hour HH:MM, for example 10:30, or 16:26 for 4:26 PM. If the person gave an hour from 1 to 12 without AM or PM, ask which before calling. Ask the user if the time is unknown; do not guess it.
birth_placeYesCity and country of birth, for example "Mumbai, India".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's contribution is the detailed inventory of what comes back — positions, house lords, Ashtakavarga/Shadbala, karakas, divisional charts, Arudhas, yogas, dasha levels, transits. That return-scope disclosure is genuinely valuable since no output schema exists, though it says nothing about payload size, cost, or failure modes for unresolvable birthplaces.

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 purpose and scope are front-loaded in the first clause, and the long middle enumeration earns its length because there is no output schema to carry that information. It is one dense sentence plus two shorter ones, with only mild redundancy between the area list in prose and the area enum.

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

Completeness4/5

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

For a six-parameter composite compute tool with no output schema, the definition covers inputs, supported areas, and the full breadth of the response, which is enough for an agent to call it correctly. The one gap is the relationship to the many single-purpose siblings, which an agent would need in order to choose this tool over them.

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

Parameters3/5

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

Schema coverage is 100% and the parameter descriptions are unusually thorough (date-order ambiguity, AM/PM ambiguity, latitude/longitude pairing rules, area enum semantics). The description adds only "Needs the birth date, time and place" and the area list, which restates the enum rather than extending it — baseline 3 is appropriate.

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?

The description names a specific verb and resource ("Calculates ... every layer of a birth chart that a question about one area of life rests on") and enumerates the supported life areas, so the agent knows exactly what the tool produces. It implies a composite/one-shot role ("in one answer") but never names a sibling like cast_birth_chart or get_arudha_padas, so differentiation is left to inference.

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?

It gives a clear trigger condition: "Use it when someone asks a real question about their life, such as how their career or marriage looks, when something may happen, or what their chart says overall," plus the prerequisite "Needs the birth date, time and place." It offers no when-not guidance and does not say when to prefer the narrower sibling tools instead.

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