Skip to main content
Glama

Tarot MCP Server by RoxyAPI

by com.roxyapi

Daily tarot card - Card of the day API

post_tarot_daily
Read-only

Receive a single tarot card for daily guidance and reflection. This endpoint uses seeded randomness to ensure the same seed gets the same card on the same day, perfect for "Card of the Day" features. Provide a seed (userId, email hash, session token) for reproducible consistency, or omit for anonymous daily draws. Returns card with keywords, full meaning, and a daily message summary. Great for tarot apps, wellness platforms, morning ritual apps, and journaling tools.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoDate for the reading in YYYY-MM-DD format. Defaults to today (UTC). Useful for viewing past daily readings or pre-generating future ones.
langNoResponse language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns English.en
seedNoOptional seed for reproducible readings. Same seed + same date = same card every time. Pass any unique identifier (userId, email hash, session token). Omit for anonymous daily readings.
compactNoSet true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.

Schema Changelog

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

  1. Changed2 schema fields changed
    • changedInput schema / properties / lang / description
      Previous value: -"Response language (ISO 639-1). Supported: en, tr, de, es, hi, pt, fr, ru. Defaults to en. Languages without translations yet return English."New value: +"Response language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns English."
    • changedInput schema / properties / lang / enum
      Previous value: -[
-  "en",
-  "tr",
-  "de",
-  "es",
-  "hi",
-  "pt",
-  "fr",
-  "ru"
-]New value: +[
+  "en",
+  "tr",
+  "de",
+  "es",
+  "hi",
+  "pt",
+  "fr",
+  "ru",
+  "zh-Hans",
+  "zh-Hant"
+]
  2. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {}
+]
    • changedInput schema / properties / compact / description
      Previous value: -"Set true to receive the exact same data in a token-optimized shape that is cheaper for you to read: whitespace is stripped and every array of same-shaped objects is encoded columnar as {\"__cols\":[field names],\"__rows\":[[values]]}, so each field name is sent once instead of once per row. Fully lossless (no field or value is dropped or changed) and typically 40 to 52 percent fewer tokens on large results. Prefer true whenever token or inference cost matters. Default false returns standard indented JSON."New value: +"Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {\"__cols\":[names],\"__rows\":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens."
  3. Changed1 schema field changed
    • changedInput schema / properties / compact / description
      Previous value: -"Return the same data in a token-optimized compact shape (minified, with same-shaped arrays encoded columnar) to reduce LLM token cost. Lossless: no fields are dropped. Default false."New value: +"Set true to receive the exact same data in a token-optimized shape that is cheaper for you to read: whitespace is stripped and every array of same-shaped objects is encoded columnar as {\"__cols\":[field names],\"__rows\":[[values]]}, so each field name is sent once instead of once per row. Fully lossless (no field or value is dropped or changed) and typically 40 to 52 percent fewer tokens on large results. Prefer true whenever token or inference cost matters. Default false returns standard indented JSON."
  4. Changed1 schema field changed
    • addedInput schema / properties / compact
      Added value: +{
+  "default": false,
+  "description": "Return the same data in a token-optimized compact shape (minified, with same-shaped arrays encoded columnar) to reduce LLM token cost. Lossless: no fields are dropped. Default false.",
+  "type": "boolean"
+}
  5. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already provide readOnlyHint=true and destructiveHint=false, covering safety. The description adds valuable behavioral context: it explains the seeded randomness mechanism ('the same seed gets the same card on the same day') and describes the return content ('keywords, full meaning, and a daily message summary'). This goes beyond annotations without contradicting them. It doesn't mention potential caveats like date validation or rate limits, but for a read-only tool this is acceptable.

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 composed of three balanced sentences. It leads with the purpose, then explains the seeding behavior, and ends with use cases. It avoids redundancy and fluff. It is slightly longer than necessary but remains focused and information-dense, earning a strong score for structure.

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?

With no output schema, the description compensates by stating what is returned ('card with keywords, full meaning, and a daily message summary'). It covers the main parameters indirectly (date, seed) and mentions language default via schema, but doesn't explicitly address the compact parameter (which schema covers). For a read-only tool with no required parameters, the description is sufficiently complete to guide correct invocation. It could have explicitly differentiated from sibling draw tools, but the 'single card' wording mitigates this.

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?

The input schema provides descriptions for all four parameters (date, lang, seed, compact), covering their formats, defaults, and examples. The description reinforces the seed purpose ('userId, email hash, session token') but does not add meaning beyond what the schema already provides. Since schema coverage is 100%, the baseline of 3 is appropriate; the tool description adds no extra parameter semantics.

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's core function: 'Receive a single tarot card for daily guidance and reflection.' It specifies the verb (receive), the resource (single tarot card), and the context (daily). It also distinguishes from siblings by emphasizing 'single card' and 'Card of the Day,' which differentiates it from multi-card draws and spreads. The mention of seeded randomness further clarifies its unique deterministic behavior.

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 description provides clear context for when to use this tool: it is 'perfect for Card of the Day features' and lists applicable use cases such as tarot apps, wellness platforms, and journaling tools. It explains the seed parameter for reproducible readings and the option to omit it for anonymous draws. However, it does not explicitly state when not to use it or name alternative sibling tools, so it misses the explicitness of the top-tier example.

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

All Tarot MCP Server by RoxyAPI toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: deck list/detail, daily draws, generic draws, four named spreads, custom spreads, and yes/no readings. Even the overlapping draw endpoints are distinguishable by their specific use cases.

Naming Consistency5/5

All tool names consistently follow a snake_case verb_tarot_resource pattern, which makes the toolset predictable and easy to navigate. The only minor oddity is get_tarot_cards_id, but it does not break the overall convention.

Tool Count5/5

Ten tools is an ideal size for a tarot API: two reference tools, one daily draw, one generic draw, four fixed spreads, one custom spread, and one yes/no tool. Each tool earns its place without overlap or bloat.

Completeness5/5

The surface covers the full tarot domain: browsing cards, retrieving detailed card interpretations, drawing cards, multiple popular spread types, custom spreads, and targeted yes/no guidance. There are no obvious dead ends or critical missing workflows.

Resources