Skip to main content
Glama
asterwise

Asterwise

Official

Tarot Card of the Day

asterwise_get_tarot_card_of_the_day
Read-onlyIdempotent

Get the daily tarot card for a date, using a date-seeded deterministic selection to reflect collective energy. Optionally enable reversed cards.

Instructions

Returns a deterministic daily tarot card seeded by SHA-256 hash of the date string. The same card is returned for all callers on the same date — this is intentional. The daily card is not a reading for an individual but a collective daily energy.

WORKFLOW: BEFORE: None — standalone. AFTER: asterwise_get_tarot_three_card_spread — for deeper daily reading context.

INPUT CONTRACT: date (optional string YYYY-MM-DD) — Date to get the card for. Defaults to today. Example: '2026-05-01' allow_reversed (optional bool) — Default: false. When true: reversed state is also deterministic (seeded by date+'_rev'). When false: card is always upright regardless of date.

DO NOT CONFUSE WITH: asterwise_draw_tarot_cards — random draw, different every call. asterwise_get_tarot_three_card_spread — positional reading with question context.

Full output and error contract: https://docs.asterwise.com/mcp/tools/get-tarot-card-of-the-day/

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoDate in YYYY-MM-DD format. Defaults to today when omitted.
allow_reversedNoWhether cards may be drawn reversed (upside down).
response_formatNoOutput format: 'markdown' (default) for a readable report, or 'json' for the raw structured payload.markdown

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the readOnly and idempotent hints, the description explains the SHA-256 seeding, deterministic behavior across callers, and the distinction from individual readings. This adds meaningful context about side effects (none) and output consistency, exceeding what annotations alone provide.

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 well-structured with clear sections (WORKFLOW, INPUT CONTRACT, DO NOT CONFUSE WITH, link to documentation) and front-loaded purpose. It is somewhat verbose, repeating schema info in prose, but the redundancy is not excessive and each section earns its place.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers purpose, parameters, workflow, alternatives, and points to a full output/error contract via URL. Given the tool's low complexity (3 simple params) and presence of an output schema, nothing is left ambiguous for a typical caller.

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 already describes all three parameters (date, allow_reversed, response_format) with 100% coverage. The description adds extra determinism detail for allow_reversed (seeded by date+'_rev') but omits any mention of response_format, missing an opportunity to clarify the JSON output. Still, it adds some value beyond 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 the tool returns a deterministic daily tarot card seeded by a date hash, and explicitly differentiates it from random draw and three-card spreads. It also clarifies the collective, non-individual nature of the reading, making the purpose unambiguous.

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

Usage Guidelines5/5

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

The description provides explicit BEFORE/AFTER workflow context and a 'DO NOT CONFUSE WITH' section naming alternative tools (random draw and three-card spread). It also notes the date defaults to today, giving concrete guidance on when to use this tool and when to avoid it.

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/asterwise/asterwise-mcp'

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