Skip to main content
Glama
astroway-mcp

astroway-mcp

Official
by astroway

RWS: Outcome Card

astroway_tarot_rider_waite_outcome
Read-onlyIdempotent

Draws a single Rider-Waite-Smith tarot outcome card for a question, with optional reversed cards and selectable art set, to clarify the likely result.

Instructions

Single outcome card.

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

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
seedNo
typeNo
drawnNo
spreadNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0

TDQS

C2.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description's one genuinely additive piece is the cost disclosure (10 credits, Tier 1) and the POST endpoint. It says nothing about determinism from the seed, rate limits, or what an "outcome card" result actually contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Very short and front-loaded, with no filler prose. But the brevity comes from under-specification rather than economy — the bracket lines carry useful cost/endpoint data while the substantive sentence says almost nothing.

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

Completeness2/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 structure needn't be explained, and annotations cover safety. However, for a 4-parameter divination tool with 25% schema coverage, the description leaves the agent without the domain framing (what "outcome" means here vs other spreads) needed to call it correctly in context.

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 25% (just `art` is documented; seed, question, and allowReversed are bare). The description contributes zero parameter meaning, so an agent gets no help deciding what to put in `question` (max 500 chars) or how `seed`/`allowReversed` shape the draw.

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

Purpose2/5

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

"Single outcome card" is a noun phrase that essentially restates the title ("RWS: Outcome Card") without a verb or any statement of what the call actually does. The group/endpoint tags confirm it is a Rider-Waite-Smith tarot draw, but nothing distinguishes it from close siblings such as draw_single, draw_decision, clarify, or timing.

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 pick this over the many other single-card RWS endpoints (draw_single, draw_decision, clarify, daily, shadow_card). The bracketed metadata gives transport and pricing facts, not selection criteria or exclusions.

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