Skip to main content
Glama
astroway-mcp

astroway-mcp

Official
by astroway

RWS: All Cards

astroway_tarot_rider_waite_cards
Read-onlyIdempotent

Retrieve all 78 Rider-Waite-Smith tarot cards with upright and reversed meanings, keywords, astrology associations, and yes/no guidance for readings.

Instructions

Full 78-card RWS deck listing with upright/reversed meanings, keywords, astrology, and yes/no affinity.

[Group: Tarot: Rider-Waite-Smith] [Endpoint: GET /v1/tarot/rider-waite/cards] [Cost: 10 credits (Tier 1)]

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": "astroway_tarot_rider_waite_cards"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
countNo
itemsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so safety is covered. The description adds genuinely new context: it enumerates the data fields bundled per card and discloses the 10-credit (Tier 1) cost, which an agent needs for budgeting. It stops short of noting payload size for a 78-card response.

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 content sentence followed by compact group/endpoint/cost metadata — front-loaded, zero padding, nothing repeated from structured fields.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 shape need not be explained, annotations carry the safety profile, and the description covers data content, cost and endpoint. Nothing an agent needs in order to call a no-arg catalog endpoint is missing.

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

Parameters4/5

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

Zero parameters, so there is nothing to disambiguate; the baseline for a no-param tool is 4. The description correctly signals that no card selector is required to obtain the whole deck.

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 resource and scope: the full 78-card RWS deck with upright/reversed meanings, keywords, astrology and yes/no affinity. 'Full 78-card' implicitly distinguishes it from the majors/minors subset siblings, though it never names the single-card sibling (cards_slug) it overlaps with.

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?

Usage is only implied — an agent can infer this is the reference-catalog endpoint to consult before or instead of drawing, but there is no explicit 'use when' statement and no routing to alternatives such as astroway_tarot_rider_waite_cards_slug or the majors/minors endpoints.

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