Skip to main content
Glama
astroway

astroway-mcp

Official

RWS — Clarifier Card

tarot_rider_waite_clarify
Read-onlyIdempotent

Draw a single clarifying Rider-Waite-Smith tarot card to provide additional insight after a primary reading. Submit a question and optional seed for deterministic results.

Instructions

Single clarifying card after a primary draw.

[Group: Tarot — Rider-Waite-Smith]

Example request body: {"seed":12345,"question":"What should I focus on?","allowReversed":true}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYesRaw JSON body — see the example in the tool description for required fields
Behavior2/5

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

Annotations already indicate read-only, idempotent, non-destructive behavior. The description only adds that it returns a single card, but does not explain the response format or additional behavioral traits such as how the card is selected or what parameters influence behavior.

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 very concise with no wasted words, immediately stating the function and providing an example. However, it could be slightly more informative without becoming verbose, such as hinting at the output.

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?

The tool has no output schema and the description omits any mention of the response structure or how to interpret the returned card. Given the simplicity of the tool, this lack of return value information leaves the agent under-informed.

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 input schema defines a generic 'body' object with no internal schema, but the description provides a concrete example with seed, question, and allowReversed, which compensates for the schema's lack of detail and guides the agent on required fields.

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

Purpose5/5

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

The description clearly states it provides a 'single clarifying card after a primary draw', using a specific verb and resource. This distinguishes it from sibling tools that perform primary draws or other tarot operations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'after a primary draw' implies sequential usage, providing clear context. However, it does not explicitly state when to use this tool over alternatives like tarot_marseille_clarify or give exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/astroway/astroway-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server