Skip to main content
Glama

Astral Code

Compare two birth charts

compare_birth_charts
Read-onlyIdempotent

Calculate synastry aspects between two user-provided birth charts. Use for relationship dynamics, communication and affinity, not a compatibility verdict or a prediction of marriage. Resolve both locations first. Unknown times exclude Moon contacts 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": {
      "person_a": "<person_a>",
      "person_b": "<person_b>"
    },
    "name": "compare_birth_charts"
  }
}

Input Schema

NameRequiredDescriptionDefault
localeNoConversation language. Default en.
person_aYes
person_bYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world, non-destructive. The description adds genuine behavioral detail beyond them: unknown birth times degrade the result by excluding Moon contacts and houses, and it pre-empts misinterpreting output as a verdict. It does not describe the shape or volume of the aspect output.

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?

Three short sentences, front-loaded with the action, then usage scope, then a prerequisite and a degradation caveat. No filler, no restatement of the title or annotations.

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 two-nested-object tool with no output schema, it covers purpose, exclusions, prerequisite ordering and the key unknown-time degradation. Remaining gaps are minor: no mention of the locale toggle or what the returned synastry aspects look like.

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?

With schema coverage reported at 33%, the description partially compensates: 'Resolve both locations first' explains the latitude/longitude/timezone requirements, and the unknown-time sentence extends the schema's 'no Ascendant or houses' with 'exclude Moon contacts'. The locale parameter and the nested person object structure go unmentioned, so meaning is added but not fully.

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?

States a specific verb and resource ('Calculate synastry aspects between two user-provided birth charts') and scopes it relative to the single-chart sibling by emphasizing 'two'. It also draws the boundary of what it is not ('not a compatibility verdict or a prediction of marriage'), so an agent can pick it correctly.

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?

Gives clear when-to-use guidance ('relationship dynamics, communication and affinity') and explicit exclusion framing (not a verdict, not a marriage prediction), plus an ordering prerequisite ('Resolve both locations first'). It stops short of naming find_birth_locations or calculate_birth_chart as the concrete alternative, leaving that inference to the agent.

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