Skip to main content
Glama

NatalChart.AI Astrology

Synastry (two charts)

synastry
Read-onlyIdempotent

Two charts compared: inter-chart aspects with orbs, house overlays both ways and a score per life sphere. (Premium or MAX) Use it when the user asks about compatibility or a relationship and gives birth data for both people.

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": {
      "personA": "<personA>",
      "personB": "<personB>"
    },
    "name": "synastry"
  }
}

Input Schema

NameRequiredDescriptionDefault
personAYes
personBYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds value beyond that by disclosing the '(Premium or MAX)' entitlement gate and sketching the response contents (orbs, two-way overlays, per-sphere scores). It omits any note on cost/latency or output size for two full charts.

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 tight sentences: the first front-loads what the tool returns, the second states the trigger condition and the required input. No filler, no restatement of the title.

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 read-only, idempotent computation with a reasonably self-documenting nested schema and no output schema, the description covers purpose, entitlement and trigger. A brief indication of the response shape or the withheld-data behavior when a birth time is null would make it fully complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is reported at 0%, and the description says nothing about personA/personB beyond 'birth data for both people'. It never explains that each person is a nested object requiring date/latitude/longitude, nor how the optional time and timezone behave, so it fails to compensate 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 names the specific operation and its outputs: inter-chart aspects with orbs, house overlays in both directions, and a score per life sphere. 'Two charts compared' implicitly distinguishes it from the single-chart natal_chart sibling, though it never names that sibling explicitly.

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?

It gives a concrete trigger: use when the user asks about compatibility or a relationship and supplies birth data for both people. That is a clear usage condition, but it offers no when-not guidance or explicit routing away from natal_chart/transits for single-person questions.

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