Skip to main content
Glama

Synastry between two people

synastry
Read-onlyIdempotent

The aspects between two people's birth charts (each one's planets to the other's), with exact orbs and strength.

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": "synastry"
  }
}

Input Schema

NameRequiredDescriptionDefault
person_aYesFirst person's birth data
person_bYesSecond person's birth data

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/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 one piece of genuine behavioral information — that the output carries exact orbs and strength values — but says nothing about volume, ordering, or what happens to angle/house-dependent results when a birth time is omitted.

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?

One sentence, front-loaded and free of filler, with the parenthetical used efficiently to define directionality. It is terse rather than padded, though the terseness is part of why other dimensions fall short.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 must carry return-value expectations, and it only hints at them ('aspects... with exact orbs and strength'). For a tool taking two full birth-data objects and producing a potentially long cross-aspect list, it leaves the shape and size of the response unclear.

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 well-documented nested birth-data objects, so the schema does the heavy lifting and a 3 is the baseline. The description contributes only the clarification that aspects run each person's planets to the other's, which helps an agent understand the two-object symmetry but adds no field-level meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource precisely — cross-aspects between two birth charts, planet-to-planet in both directions — which is more specific than the title. But it is a bare noun phrase with no verb (compute/calculate/return), and it never contrasts itself with natal_chart or transits, the siblings an agent would most likely confuse it with.

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 statement of when to use this rather than natal_chart (one chart) or transits (one chart against the sky). An agent must infer the distinction from the phrase 'between two people' alone, and no prerequisites or exclusions are given.

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