astroway-mcp

Official

by astroway

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Owner-Pet Compatibility

astroway_pet_owner_pet_compatibility

Read-onlyIdempotent

Calculates a 0-100 astrological compatibility score between a pet and its owner using element and sign distance. Provide both birth charts to reveal relationship dynamics.

Instructions

Compatibility score (0-100) based on element + sign distance.

[Group: Pet Astrology] [Endpoint: POST /v1/pet/owner-pet-compatibility] [Required: owner, pet] [Cost: 10 credits (Tier 1)]

Input Schema

Name	Required	Description	Default
`pet`	Yes	Birth data for a single natal chart. Required: date (YYYY-MM-DD), time (HH:mm:ss), latitude and longitude in decimal degrees. The short forms lat, lon, lng and tz are rejected with 400 INVALID_FIELD; pass the full names. timezoneOffset is hours from UTC and defaults to 0, meaning UTC; send timezone instead (an IANA name such as Europe/Kyiv, or auto) and the offset for that date is worked out, summer time included. city is a display label only: nothing here geocodes it, so it never stands in for coordinates. houseSystem is a single Swiss Ephemeris letter, P by default; a name such as "Placidus" is refused, and the case matters because I and i are two different Sunshine systems.
`owner`	Yes	Birth data for a single natal chart. Required: date (YYYY-MM-DD), time (HH:mm:ss), latitude and longitude in decimal degrees. The short forms lat, lon, lng and tz are rejected with 400 INVALID_FIELD; pass the full names. timezoneOffset is hours from UTC and defaults to 0, meaning UTC; send timezone instead (an IANA name such as Europe/Kyiv, or auto) and the offset for that date is worked out, summer time included. city is a display label only: nothing here geocodes it, so it never stands in for coordinates. houseSystem is a single Swiss Ephemeris letter, P by default; a name such as "Placidus" is refused, and the case matters because I and i are two different Sunshine systems.

Output Schema

Name	Required	Description	Default
`compatibility`	No

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.6.0Oct 24, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior. The description adds the 10-credit cost tier and POST endpoint, which are useful behavioral details beyond annotations, though it omits auth or rate-limit 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?

One front-loaded sentence states the score, range, and method; the bracketed metadata is terse and scannable. No 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?

Given rich nested schemas, an output schema, and annotations, the description covers the score range, basis, required inputs, and cost. It leaves the relationship to other compatibility tools implicit, which is a minor but real gap.

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% and the nested birth-data objects are heavily documented, so the schema carries the parameter meaning. 'Required: owner, pet' repeats schema requirements without adding syntax or interpretation.

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 computed output (a 0-100 compatibility score) and the factors behind it (element + sign distance), and the required owner/pet pair distinguishes it from generic compatibility siblings. It does not explicitly name the sibling it could be confused with, so it falls short of a 5.

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?

No sentence says when to use this rather than astroway_horoscope_compatibility, astroway_relational_match_score, or the other pet tools; 'Required: owner, pet' only restates schema requirements. The Pet Astrology group implies context, but there is no explicit usage guidance or exclusion.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server