AstroWay Tarot

RWS: Single Card Draw

astroway_tarot_rider_waite_draw_single

Read-onlyIdempotent

Draw 1 card from the RWS deck. Optional seed for deterministic shuffle.

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

Input Schema

Name	Required	Description
`art`	No	Card art set, e.g. rws-1909, rws-restored, rws-vector. GET /v1/tarot/decks lists the sets per deck.
`seed`	No
`fields`	No	Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response.
`question`	No
`precision`	No	Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.
`allowReversed`	No

Output Schema

Name	Required	Description	Default
`seed`	No
`drawn`	No
`spread`	No
`localized`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 6, 2026

addedInput schema / properties / art

Added value: +{
+  "description": "Card art set, e.g. rws-1909, rws-restored, rws-vector. GET /v1/tarot/decks lists the sets per deck.",
+  "maxLength": 40,
+  "type": "string"
+}

First observedOct 5, 2026

TDQS

B3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds useful context by explaining the seed's purpose ('deterministic shuffle') and disclosing cost (10 credits) and endpoint, but it says nothing about reversal behavior or how the draw is reported.

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 core action and the seed hint are front-loaded in one tight sentence, and the bracketed group/endpoint/cost block is compact and useful metadata. Nothing is padded, though the metadata block is somewhat formulaic.

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 explained, and annotations cover safety. The description covers purpose, cost, and the seed's determinism, but leaves half the parameters and the reversal behavior unaddressed, which is thin for a six-parameter draw 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 coverage is only 50%: seed, question, and allowReversed have no descriptions in the schema. The description rescues only one of them by explaining the seed as a deterministic shuffle control, leaving 'question' and 'allowReversed' undocumented in both places. Given six parameters and half left undefined, this does not fully compensate for the coverage gap.

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 gives a specific verb+resource ('Draw 1 card from the RWS deck') and the title reinforces the deck and single-card scope, so an agent can distinguish it from the many tarot draw siblings. It stops short of explicitly differentiating from adjacent tools like draw_three_card or the Marseille draw_single, so it is clear but not fully sibling-differentiated.

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?

Beyond 'Draw 1 card,' there is no guidance on when to choose this tool versus the other RWS spread tools (three_card, celtic_cross, love_triangle, etc.) or the Marseille single draw. The tool's place among siblings must be inferred entirely from the name.

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

All AstroWay Tarot tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?