Skip to main content
Glama

Compare two charts

get_compatibility
Read-onlyIdempotent

Compares two birth charts: the two people's Sun, Moon and rising signs, the closest contacts between their planets with what each traditionally means, and how their elements balance. It returns a score out of 100, scores for attraction, communication and long-term stability, a verdict, a headline and a "Reading confidence NN%" label that says how specific the details were, not the odds of an event. One side can be a famous person whose chart Zodiacs publishes. shareUrl is the link for sharing the score. It fits a question about compatibility between two adults, or between a person and a published famous person. The score is astrology's reading of two charts, not a guarantee of how a relationship will go. Limits: it compares two adults, so when either birth date is under 18 there is no love or romance reading and no score. It refuses a birth date less than 13 years ago. Each person needs a birth date; without a birth time and place there is no rising sign. A famous person's chart is for noon on their birth date, with no Moon or rising sign, and an unknown name returns found: false. Birth details are used for this answer only: never stored, logged or put in a link. Its results include a link inviting a partner to compare charts on the site.

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": {
      "a": "<a>",
      "b": "<b>"
    },
    "name": "get_compatibility"
  }
}

Input Schema

NameRequiredDescriptionDefault
aYesThe first person.
bYesThe second person, or { famous: "<name>" } for a famous person Zodiacs publishes.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only cover the safety profile (readOnly, idempotent, non-destructive, closed world), yet the description adds refusal thresholds, the fact that a famous chart is fixed at noon with no Moon or rising sign, that an unknown name returns found: false, data-retention guarantees (never stored, logged or linked), and the output's referral link. It also pre-empts a likely misreading by defining 'Reading confidence NN%' as detail specificity rather than odds.

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?

Front-loaded with purpose, then outputs, then limits — a sensible order for an agent. It is long, but nearly every sentence carries a non-obvious constraint or disambiguation; the only mild slack is restating output contents that the output schema may already cover.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-nested-object, dual-mode (birth details vs. famous name) tool with an output schema, the description covers input preconditions, refusals, degenerate cases (no birth time → no rising sign; unknown famous name), privacy, and the semantics of the returned confidence label. Nothing an agent needs to call it correctly appears to be missing.

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 100%, so field-level meaning is already documented and the baseline is 3. The description still adds conditional logic the schema does not state as a whole: each person needs a birth date, a birth time and place are required for a rising sign, and 'famous' substitutes for all other fields. That is meaningful cross-field guidance beyond per-property text.

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?

Opens with a specific verb and resource ('Compares two birth charts') and enumerates the actual outputs: signs, inter-planet contacts, element balance, a score out of 100 plus sub-scores, verdict and headline. An agent can distinguish this from single-chart siblings like get_natal_chart or get_famous_chart without opening any schema.

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

Usage Guidelines5/5

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

Explicitly states the fitting question ('compatibility between two adults, or between a person and a published famous person') and gives hard exclusions: no love/romance reading or score when either birth date is under 18, and refusal of birth dates less than 13 years ago. It also explains the famous-person alternative path, so the agent knows when to switch input modes.

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.