Skip to main content
Glama

Asteria: Astrology & Tarot

Birth chart (natal chart)

birth_chart
Read-onlyIdempotent

Computes a natal chart from a birth date, with optional birth time and place: the sign and degree of the Sun, Moon, Mercury, Venus, Mars, Jupiter, Saturn, Uranus, Neptune, Pluto, Chiron and the North Node, the major aspects between them, and, when the time, time zone and coordinates are given, the Ascendant (rising sign), Midheaven, the twelve Placidus houses and the house of each planet. Returns the full reading of the Sun, Moon and rising sign (the big three) and a one-line reading of every other placement. Use it for any question about someone's birth chart, big three, or planets in signs and houses.

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": {
      "date": "<date>"
    },
    "name": "birth_chart"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesBirth date, YYYY-MM-DD.
timeNoBirth time on the local clock of the birth place, HH:MM (24-hour). Optional when unknown.
languageNoLanguage of the readings: en, fr, es, pt-BR, ja or de (default en). Use the language of the conversation.
latitudeNoLatitude of the place of birth (where the person was born, never where the user is now), degrees, north positive.
timezoneNoIANA time zone of the birth place (e.g. Europe/Paris, America/New_York, America/Sao_Paulo). Required with a time.
longitudeNoLongitude of the place of birth (where the person was born, never where the user is now), degrees, east positive.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile is covered. The description adds real value beyond that: it discloses the conditional degradation (Ascendant, Midheaven and houses appear only when time, time zone and coordinates are supplied) and the shape of the return (full readings for the big three, one-line readings for the rest). It still says nothing about failure modes for malformed dates or time zone mismatches.

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?

Content is front-loaded and every clause carries information; there is no filler or marketing language. The main drawback is density — the first sentence runs long by listing each celestial body, which could have been compressed into a category label.

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?

With no output schema, the description correctly takes on the burden of describing return values, and it does so at the right granularity for a 6-parameter tool. The conditional output behavior is spelled out. Only error handling and any computational caveats (e.g. unknown time fallbacks) are left unaddressed.

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%, so every parameter already carries its own description, including the note that timezone is 'Required with a time' and that latitude/longitude are the birth place, not the user's location. The description restates the time/time zone/coordinate dependency that unlocks houses, but adds no syntax, format or edge-case detail the schema lacks. Baseline 3 is appropriate.

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?

The description opens with a specific verb and resource ('Computes a natal chart from a birth date') and then enumerates exactly what is produced: twelve bodies, major aspects, and conditionally the Ascendant, Midheaven and Placidus houses. That enumeration makes it obviously the comprehensive counterpart to single-placement siblings like sun_sign, moon_sign and rising_sign, so an agent can route without opening a 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?

The final sentence gives an explicit when-to-use rule: 'any question about someone's birth chart, big three, or planets in signs and houses.' However, it never tells the agent when to prefer the lighter siblings (sun_sign, moon_sign, rising_sign) that cover the same 'big three' ground, and no when-not guidance is offered.

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.