Skip to main content
Glama
astroway-mcp

astroway-mcp

Official
by astroway

RWS: Court Card Cross-Sum

astroway_tarot_rider_waite_cross_sum
Read-onlyIdempotent

Generate a birth-card meditation pair for Tarot court-card practice from a date, with optional card art selection.

Instructions

Birth-card meditation pair for court-card practice.

[Group: Tarot: Rider-Waite-Smith] [Endpoint: POST /v1/tarot/rider-waite/cross-sum] [Required: date] [Cost: 10 credits (Tier 1)]

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": {
      "date": "<date>"
    },
    "name": "astroway_tarot_rider_waite_cross_sum"
  }
}

Input Schema

NameRequiredDescriptionDefault
artNoCard art set, e.g. rws-1909, rws-restored, rws-vector. GET /v1/tarot/decks lists the sets per deck.
dateYes

Output Schema

NameRequiredDescriptionDefault
dateNo
meditationPairNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so safety is covered. The description adds genuinely useful operational context — the POST endpoint and the cost of 10 credits (Tier 1) — but says nothing about whether the result is deterministic from the date, how large the response is, or how the pair relates to the cross-sum.

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?

One sentence, front-loaded, with no filler. The bracketed metadata block is boilerplate but compact and surfaces the endpoint, required parameter, and credit cost without burying the purpose.

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?

An output schema exists, so return values need not be spelled out, and annotations cover safety. However, for a date-driven tarot computation adjacent to several overlapping RWS tools, the description leaves the core semantics of the "cross-sum" undefined, which is a meaningful gap for correct invocation.

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 50%: 'art' is documented in the schema, while 'date' has only a pattern and required flag. The description partially compensates by framing the date as a birth date ("Birth-card"), but it never states the date's role explicitly or mentions the optional art selection, so an agent must still infer meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The phrase "Birth-card meditation pair for court-card practice" hints at the output (a pair of cards tied to a birth date) but contains no verb describing what the tool actually computes or returns. It does not distinguish itself from siblings such as astroway_tarot_rider_waite_birth_card, astroway_tarot_rider_waite_courts, or astroway_tarot_rider_waite_soul_personality_card, so an agent cannot reliably pick it on purpose alone.

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 guidance, no exclusions, and no named alternative. The only routing signal is the implicit "court-card" framing and the required date, leaving the agent to infer that this is a birth-date-driven court-card pairing rather than a draw or lookup.

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

Deploy Server

Other Tools