Skip to main content
Glama
astroway-mcp

astroway-mcp

Official
by astroway

RWS: All Spreads

astroway_tarot_rider_waite_spreads
Read-onlyIdempotent

Retrieve all 12 Rider-Waite-Smith tarot spread definitions to compare layouts and choose the right spread for a reading.

Instructions

List of all 12 RWS spread definitions.

[Group: Tarot: Rider-Waite-Smith] [Endpoint: GET /v1/tarot/rider-waite/spreads] [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_spreads"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
countNo
itemsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare this as a read-only, idempotent, non-destructive, closed-world operation. The description adds useful context by naming the result cardinality (12 spreads) and the credit cost, but it otherwise does not describe return structure or how to use the result for subsequent draws.

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?

The description is short and front-loaded with the essential purpose. The bracketed metadata lines for group, endpoint, and cost are compact and useful, though slightly more than the minimal description needed.

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?

For a zero-parameter catalog endpoint with an output schema, the description is largely complete: it states what is returned and the cost. It could add a pointer to the spread-slug lookup or draw tools, but the core information needed to invoke it is present.

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?

The tool has zero parameters, so there is no parameter semantics to explain. The empty schema is self-explanatory, and the description does not need to compensate for undocumented 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?

The description clearly states the specific resource and scope: all 12 Rider-Waite-Smith spread definitions. It is distinguishable from draw tools, but it does not explicitly differentiate itself from the sibling `astroway_tarot_rider_waite_spreads_slug`, which likely retrieves a single spread by slug.

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 guidance on when to use this tool versus alternatives such as spread-by-slug lookup or the many draw tools. The description only states what the endpoint returns, leaving the agent to infer that this is a discovery/catalog call.

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