Skip to main content
Glama

Birth chart

natal_chart
Read-onlyIdempotent

A complete natal (birth) chart: every planet's sign, degree and house, the Ascendant and Midheaven, retrogrades, and the aspects between planets with exact orbs. Calculated from NASA JPL data by Naelos Ephemeris.

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>",
      "latitude": "<latitude>",
      "longitude": "<longitude>",
      "timezone": "<timezone>"
    },
    "name": "natal_chart"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesBirth date, YYYY-MM-DD
timeNoLocal clock time, HH:MM (24-hour). If unknown, omit: noon is used, and houses and angles are then unreliable.
placeNoBirthplace name, echoed back so the user can check the coordinates
latitudeYesBirthplace latitude in decimal degrees (north positive)
timezoneYesIANA time zone of the birthplace, e.g. America/New_York. Historical daylight saving is applied from it.
longitudeYesBirthplace longitude in decimal degrees (east positive)
house_systemNoHouse system (default placidus)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=false, so the safety profile is covered. The description adds real value by disclosing the computation source (NASA JPL data via Naelos Ephemeris) and the completeness of the returned data. It says nothing, however, about determinism, latency, or failure modes — and the important caveat that omitting `time` degrades houses and angles lives only in the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the payload contents and followed by provenance. There is no filler, and the second sentence earns its place by establishing data reliability.

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 carries the burden of explaining return values and does so thoroughly by listing the chart components. It is nearly complete, but a small gap remains: the consequence of omitting `time` and the effect of `house_system` on the output are not surfaced in the description.

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 description coverage is 100%, with every parameter including the nine-value house_system enum documented in-schema, so the baseline is 3. The description adds no parameter-level meaning beyond the schema — it never mentions the time-omission fallback or the default house system.

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 concrete resource — a complete natal chart — and enumerates its contents (planets, signs, degrees, houses, ASC/MC, retrogrades, aspects with orbs), so an agent knows exactly what it produces. It does not name a sibling or state why it differs from planet_position or synastry, so it falls short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance, and no alternative is mentioned despite nine siblings including planet_position and synastry, which overlap substantially. The agent must infer selection from the tool name alone.

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