Skip to main content
Glama

Birth chart readout

get_natal_chart
Read-onlyIdempotent

Reads one person's birth chart in the conversation: the Sun, Moon and rising signs, each planet's sign and degree, its house when the birth time and place are known, the closest aspects between the planets, and the balance of elements and modes, each with what astrology traditionally reads into it. It fits someone who has already given their birth date and wants the chart read out; open_chart_studio is the panel for filling one in. A chart, a rising sign or a Moon sign asked for with no birth date in the conversation belongs to open_chart_studio, which opens with no details: the person enters them there, so nothing has to be asked for first. Without a birth time it gives no rising sign and no houses, and on a day the Moon changed sign it gives the Moon sign as two possibilities. The rising sign and houses also need the birthplace's latitude, longitude and time zone, which find_birthplace returns for a town or city. When the birth time fell in a skipped or repeated hour of a clock change, timeNote says which instant was used. Birth dates run from 1800 to 2199. It refuses a birth date less than 13 years ago, so it also refuses a chart for today or for a recent moment; for the sky at a moment there is get_sky. For a birth date under 18 romantic and attraction readings are left out and a note says so. chartUrl opens the birth chart page and carries no birth date, time, place or coordinates.

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": {
      "birthDate": "<birthDate>"
    },
    "name": "get_natal_chart"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeNoThe birth time on the local clock, such as 08:30, only if the person knows it. Never guess it. Needs zone.
zoneNoThe birthplace's time zone, such as Europe/Madrid. Needed with a time or a place.
placeNoOptional birthplace name, such as Madrid, Spain. Display only: it is not used in the calculation and is not stored.
latitudeNoOptional. The birthplace's latitude; with a birth time it adds the rising sign and the houses. Give it with longitude and zone. Nothing is stored.
birthDateYesThe birth date, such as 1990-05-03 (years 1800 to 2199).
longitudeNoOptional. The birthplace's longitude, with latitude. Nothing is stored.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/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), yet the description still adds substantial behavior: missing birth time yields no rising sign or houses, ambiguous Moon sign on sign-change days, timeNote for skipped/repeated DST hours, the 1800–2199 range, refusal of birth dates under 13 years ago, and omission of romantic readings for minors. It stops short of describing the return shape or how the two-Moon-sign case is structured, but the disclosure is far above the annotation bar.

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 core capability and the primary alternative are front-loaded in the first two sentences, and the remaining edge cases each carry operational weight (DST notes, minor filtering, date bounds, PII-free chartUrl). It is a dense unbroken block, though; splitting the caveats from the routing guidance would make it scannable without cutting content.

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 six-parameter read tool with a full schema and an output schema, the description covers everything an agent needs before calling: required date, optional time/place/coordinates and their effects, degraded-output cases, refusal conditions, and the PII property of the returned URL. Return-value formatting is rightly 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%, so 3 is the floor, but the description adds causal meaning the schema only implies: latitude plus time is what produces the rising sign and houses, the zone is required alongside time or place, and find_birthplace is the source for coordinates. It does not clarify how place/zone interact when only a place name is supplied, which keeps it below a 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?

The opening sentence names a specific verb and resource (reads one person's birth chart) and enumerates exactly what the readout contains: Sun/Moon/rising, planet sign and degree, houses, closest aspects, element and mode balance. It explicitly distinguishes itself from open_chart_studio (the intake panel) and get_sky (the sky at a moment), so an agent can route correctly without opening schemas.

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?

Usage conditions are stated in both directions: it fits someone who has already given a birth date, while a chart requested with no birth date belongs to open_chart_studio, and a moment-sky request belongs to get_sky. It even explains why open_chart_studio is the right fallback (it opens with no details, so nothing must be asked for first). find_birthplace is named for the coordinate lookup prerequisite.

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.