Skip to main content
Glama

AstroWay Core astrology

Compatibility Horoscope

astroway_horoscope_compatibility
Read-onlyIdempotent

Generate a relationship horoscope based on synastry between two charts: strengths, friction points, and themes for the next 30 days.

[Group: Horoscope] [Endpoint: POST /v1/horoscope/compatibility] [Required: sign1, sign2] [Cost: 50 credits (Tier 3)]

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": {
      "sign1": "<sign1>",
      "sign2": "<sign2>"
    },
    "name": "astroway_horoscope_compatibility"
  }
}

Input Schema

NameRequiredDescriptionDefault
sign1Yes
sign2Yes
fieldsNoCompact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response.
languageNo
precisionNoCompact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.
disclaimer_inlineNo

Output Schema

NameRequiredDescriptionDefault
scoreNo
summaryNo
languageNo
strengthsNo
challengesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • changedOutput schema / properties / challenges / anyOf
      Previous value: -[
      -  {
      -    "items": {
      -      "anyOf": [
      -        {
      -          "type": "string"
      -        },
      -        {
      -          "type": "null"
      -        }
      -      ]
      -    },
      -    "type": "array"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "items": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedOutput schema / properties / language / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / language / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / score / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / score / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • changedOutput schema / properties / strengths / anyOf
      Previous value: -[
      -  {
      -    "items": {
      -      "anyOf": [
      -        {
      -          "type": "string"
      -        },
      -        {
      -          "type": "null"
      -        }
      -      ]
      -    },
      -    "type": "array"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "items": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedOutput schema / properties / summary / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / summary / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  2. First observed

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's added value is the cost disclosure — 50 credits, Tier 3 — plus the concrete endpoint and the 30-day scope of the output. Those are things an agent cannot see in the annotations and that materially affect invocation decisions. It does not disclose rate limits, error behavior, or whether the two signs may be identical.

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?

A single substantive sentence followed by compact bracketed metadata; the purpose is front-loaded and nothing is padded. The metadata lines are terse and each carries operational information (group, endpoint, required fields, cost).

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 an output schema present, the description needn't detail return values, yet it usefully names the three content areas and the 30-day window. What is missing is meaningful coverage of the four optional parameters and a reconciliation of "two charts" with the sign-based inputs, which leaves gaps for a 6-parameter tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33%: sign1 and sign2 carry no descriptions beyond their enums, and language and disclaimer_inline are entirely undocumented. The description only repeats the required set already declared in the schema and does not explain sign ordering, what disclaimer_inline toggles, or how language affects output. It also describes the input as "two charts", which contradicts the sign-based parameters.

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?

States a specific verb and resource ("Generate a relationship horoscope") plus the analytic basis (synastry) and the output dimensions (strengths, friction points, 30-day themes). That clearly separates it from astroway_horoscope_daily/weekly/monthly/yearly, which are single-sign time horoscopes. The only blur is the phrase "between two charts" when the inputs are actually two zodiac signs, not chart data.

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 when-to-use or when-not-to-use guidance and no named alternative among the many horoscope siblings. The "[Group: Horoscope]" tag implies the family but does not tell an agent why to pick compatibility over daily/weekly/monthly/yearly. The implied trigger (two people's signs) is left for the agent to infer.

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