Skip to main content
Glama
astroway

astroway-mcp

Official

RWS — Daily Card

tarot_rider_waite_daily
Read-onlyIdempotent

Get a daily Rider-Waite-Smith tarot card based on a given date. The card is the same for all queries on that day.

Instructions

Daily card based on date seed (deterministic per day).

[Group: Tarot — Rider-Waite-Smith]

Example request body: {"date":"2026-05-04"}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYesDate YYYY-MM-DD
latitudeNoLatitude (some date-only endpoints accept location)
longitudeNoLongitude
timezoneOffsetNoUTC offset in hours
Behavior4/5

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

Annotations already indicate readOnly, idempotent, non-destructive. The description adds that results are deterministic per day based on date seed, providing useful behavioral context beyond annotations. However, it does not describe the output format.

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?

The description is extremely concise (two sentences plus an example and group tag). No unnecessary words, front-loaded with the core purpose.

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 simple tool with one required parameter and no output schema, the description covers determinism, date seed, and group. It could be improved by hinting at the output (e.g., 'returns a single tarot card'), but is adequate.

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

Parameters3/5

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

Schema coverage is 100%, so the schema already documents all parameters. The description provides a useful example request but adds minimal semantic nuance beyond what is in the schema.

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 daily card based on a date seed, with group identification. This distinguishes it from other tarot draw tools by emphasizing determinism and daily use.

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?

No guidance on when to use this tool versus other tarot draw tools (e.g., single draw, Celtic cross). The description does not mention alternatives or specify context of use.

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