Skip to main content
Glama

Get Chinese Astrology

Animal compatibility

check_animal_compatibility
Read-onlyIdempotent

Compares two Chinese zodiac animals, or the animals of two birth years, and names their relationship: Six Harmony, Three Harmony, clash, harm, break, punishment or neutral. Returns the relation types, the phase interaction, the distance on the twelve-animal circle and a written reading of the pair.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "check_animal_compatibility"
  }
}

Input Schema

NameRequiredDescriptionDefault
firstYearNoFirst birth year from 1901 to 2100, paired with secondYear.
secondYearNoSecond birth year from 1901 to 2100, paired with firstYear.
firstAnimalNoFirst zodiac animal, paired with secondAnimal.
secondAnimalNoSecond zodiac animal, paired with firstAnimal.

Output Schema

NameRequiredDescriptionDefault
itemYes
viewYes
requestYes

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 establish read-only, idempotent, closed-world, non-destructive behavior, and the description adds domain-specific output categories (Six Harmony, clash, phase interaction, distance, reading). It does not discuss valid parameter combinations or edge cases, but for an annotated read-only computation this is solid additional context.

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 comparison, then the returned relation details; no filler. The enumerated relationship list is dense but directly useful.

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?

The tool has annotations, a complete schema, and an output schema, so the description need not explain return structure in detail. It conveys the core comparison and outputs, but with zero required parameters it leaves the exact valid pairing/mixing rules implicit.

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%, so ranges, enums, and pairing notes are already documented in the schema. The description adds the alternative input modes (animals vs. birth years) and implies years map to animals, but it does not clarify whether animal and year parameters may be mixed or exactly which pair is required.

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 states a specific verb and resource ('compares two Chinese zodiac animals...') and enumerates the relationship outcomes, so the operation is unambiguous. It stops short of naming or distinguishing a sibling such as get_zodiac_year, so it is clear but not sibling-differentiating.

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

Usage Guidelines3/5

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

It implies the tool is for pair comparisons using either animal names or birth years, which is enough to infer basic use. It gives no explicit 'use this when' guidance, no exclusions, and no alternative tool routing against get_zodiac_year or other siblings.

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.