Skip to main content
Glama

Astral Code

Birth chart · Sun, Moon & Rising

calculate_birth_chart
Read-onlyIdempotent

Calculate a tropical Placidus natal chart, Big Three, positions and aspects from user-provided birth details. Resolve the city first. Ask for missing details; never guess birth time. Returns a chart here and an optional link to continue on Astral Code. Astrology is symbolic reflection, not a prediction of events.

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": "<birth>"
    },
    "name": "calculate_birth_chart"
  }
}

Input Schema

NameRequiredDescriptionDefault
birthYes
localeNoConversation language. Default en.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorldHint=false, so the safety profile is covered. The description adds context those annotations don't: it explains what comes back (the chart here plus an optional link to continue on Astral Code) and notes that unknown birth time omits the Ascendant and houses. The disclaimer about astrology being symbolic reflection is useful scoping, though the return format stays high level.

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?

Four short sentences with no filler. The order is logical: what it does, the prerequisite, the missing-input rule, the output, then the caveat. Each sentence adds new information.

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?

No output schema exists, so the description has to say what comes back, and it does at a high level. For a nested, coordinate-heavy input with 50% schema coverage, marketing the required upstream resolution step helps. Some parameter detail, notably coordinates and locale, is left to the schema or left unstated.

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 50%: timezone, birth_date, birth_time and unknown_time carry descriptions, but latitude, longitude, birthplace and locale do not. The description partly fills that gap: 'Resolve the city first' connects birthplace and the coordinates to find_birth_locations, and 'never guess birth time' reinforces the birth_time/unknown_time pairing. It doesn't explain coordinate conventions or the locale field, so it isn't fully compensating for the coverage gap.

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 opens with a specific verb and resource: 'Calculate a tropical Placidus natal chart, Big Three, positions and aspects' from birth details. That distinguishes it clearly from get_moon_phase and compare_birth_charts. It doesn't name a sibling outright, so it falls just short of 5.

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?

'Resolve the city first' and 'Ask for missing details; never guess birth time' give concrete preconditions and an explicit prohibition, which is real usage guidance. It stops short of naming an alternative tool to call, and it doesn't spell out when not to use it, which keeps it at 4 rather than 5.

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