Skip to main content
Glama

Asteria: Astrology & Tarot

Zodiac compatibility (love)

sign_compatibility
Read-onlyIdempotent

Reads the love compatibility of two zodiac signs: what draws them together, their strengths as a couple, what can go wrong between them. Use it for questions such as « are Leo and Aries compatible? ».

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": {
      "sign_a": "<sign_a>",
      "sign_b": "<sign_b>"
    },
    "name": "sign_compatibility"
  }
}

Input Schema

NameRequiredDescriptionDefault
sign_aYesFirst zodiac sign.
sign_bYesSecond zodiac sign.
languageNoLanguage of the readings: en, fr, es, pt-BR, ja or de (default en). Use the language of the conversation.

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 this a safe, idempotent, closed-world read, so the description need not restate that; instead it adds genuinely new context by sketching the shape of the response (what draws them together, strengths, risks), which matters because there is no output schema. It doesn't discuss length or formatting of the reading, which keeps it short of a 5.

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 sentences, front-loaded with the capability and followed immediately by the example query. Nothing is repeated from the schema and no sentence is filler.

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 simple three-parameter read-only lookup with fully documented enums, the definition covers purpose, trigger example, and the substance of the answer. The only marginal gap is that it doesn't say how long or in what form the reading arrives, though the language parameter already signals localized prose output.

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 coverage is 100% with all three parameters enumerated and described, including the default and the instruction to match the conversation language. The description only reinforces that two signs are involved and does not add syntax or pairing-order guidance, so the schema carries the load and the baseline 3 applies.

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?

The description names a specific verb and resource ('Reads the love compatibility of two zodiac signs') and enumerates the three content areas returned: attraction, strengths as a couple, and pitfalls. That scope clearly separates it from the sibling tools, which deal with single placements (sun_sign, moon_sign, rising_sign), full charts, or tarot.

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 supplies a concrete triggering question ('are Leo and Aries compatible?'), which gives an agent a direct pattern to match at routing time. There is no explicit when-not-to-use clause or named alternative, but the love-pair framing is narrow enough that no real ambiguity with the placement or tarot siblings remains.

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.