Tarot MCP Server by RoxyAPI

List all 78 tarot cards - Tarot deck catalog API

get_tarot_cards

Read-only

Retrieve the complete Rider-Waite-Smith tarot deck of 78 cards. The 22 Major Arcana (numbered 0-21) carry life lessons, spiritual themes, and karmic influences like The Fool, Death, The Tower; the 56 Minor Arcana (4 suits × 14 cards each) cover daily situations and practical matters. Filter by arcana type (major for spiritual guidance, minor for everyday concerns), suit (cups for emotions and relationships, wands for creativity and passion, swords for intellect and conflict, pentacles for material wealth and finances), or card number (Ace=1 for new beginnings, 2-10 for progression, Page=11 for messages, Knight=12 for action, Queen=13 for mastery, King=14 for authority). Returns lightweight basic card data. Use GET /cards/{id} for full upright and reversed interpretations with keywords. Perfect for building tarot reference libraries, card databases, learning applications, or browsing the complete traditional deck used by professional tarot readers worldwide.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`lang`	No	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.	en
`suit`	No	Filter minor arcana by suit. Cups=emotions/relationships, Wands=creativity/passion, Swords=intellect/conflict, Pentacles=material/finances. Only applies to minor arcana cards.
`limit`	No	Maximum items to return per page. Range: 1-100, default 20.
`arcana`	No	Filter by arcana type. Major arcana (0-21) represents life lessons and spiritual themes. Minor arcana (Ace-King in 4 suits) represents daily situations and practical matters.
`number`	No	Filter by card number. Major Arcana: 0 (The Fool) through 21 (The World). Minor Arcana: 1 (Ace) through 14 (King). Combine with arcana or suit filters for precise results.
`offset`	No	Number of items to skip for pagination. Default 0.
`compact`	No	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.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`cards`	Yes
`limit`	Yes
`total`	Yes
`offset`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 23, 2026
- addedInput schema / properties / number / maximum
```
Added value: +21
```
- addedInput schema / properties / number / minimum
```
Added value: +0
```
- addedInput schema / properties / offset / default
```
Added value: +0
```
- addedInput schema / properties / offset / minimum
```
Added value: +0
```
Changed6 schema fields changedSep 20, 2026
- removedInput schema / properties / number / maximum
```
Removed value: -21
```
- removedInput schema / properties / number / minimum
```
Removed value: -0
```
- changedInput schema / properties / number / type
```
Previous value: -[
-  "integer",
-  "null"
-]New value: +"integer"
```
- removedInput schema / properties / offset / default
```
Removed value: -0
```
- removedInput schema / properties / offset / minimum
```
Removed value: -0
```
- changedInput schema / properties / offset / type
```
Previous value: -[
-  "integer",
-  "null"
-]New value: +"integer"
```

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "cards": {
+      "items": {
+        "properties": {
+          "arcana": {
+            "enum": [
+              "major",
+              "minor"
+            ],
+            "type": "string"
+          },
+          "id": {
+            "type": "string"
+          },
+          "imageUrl": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "number": {
+            "type": "number"
+          },
+          "suit": {
+            "enum": [
+              "cups",
+              "wands",
+              "swords",
+              "pentacles"
+            ],
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "name",
+          "arcana",
+          "number",
+          "imageUrl"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "limit": {
+      "type": "number"
+    },
+    "offset": {
+      "type": "number"
+    },
+    "total": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "total",
+    "limit",
+    "offset",
+    "cards"
+  ],
+  "type": "object"
+}

Changed1 schema field changedSep 19, 2026

changedInput schema / properties / number / type

Previous value: -[
-  "number",
-  "null"
-]New value: +[
+  "integer",
+  "null"
+]

Changed2 schema fields changedAug 25, 2026

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"
+]

Changed2 schema fields changedAug 17, 2026

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."

Changed2 schema fields changedAug 2, 2026

changedInput schema / properties / number / type

Previous value: -"number"New value: +[
+  "number",
+  "null"
+]

changedInput schema / properties / offset / type

Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]

Changed1 schema field changedJul 22, 2026

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."

Changed1 schema field changedJul 22, 2026

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"
+}

First observedJul 8, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds behavioral context: it returns 'lightweight basic card data' and points to GET /cards/{id} for full interpretations, thereby disclosing what this endpoint does not return. It also describes the deck contents and filter semantics. No contradiction with annotations.

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?

The description is front-loaded with the core purpose, which is good. However, it is verbose, repeats a lot of schema-provided filter detail, and ends with a promotional sentence ('Perfect for building tarot reference libraries... used by professional tarot readers worldwide') that does not earn its place. It is not tight enough for a 5, but the main content is relevant enough for a 3.

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?

Given the rich input schema (7 parameters, 100% coverage, enums), the true output schema, and read-only annotations, the description does not need to explain return structure or pagination mechanics. It provides sufficient narrative context about what the deck contains, how to filter, and when to use the detail endpoint. No critical usage information is missing.

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?

Schema description coverage is 100%, so the baseline is 3. However, the description adds meaning beyond the schema: it maps number values to named cards (Page=11 for messages, Knight=12 for action, Queen=13 for mastery, King=14 for authority), expands suit meanings, and clarifies arcana significance in ways the schema only summarizes. This extra semantic layer earns a 4.

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 opens with a specific verb and resource: 'Retrieve the complete Rider-Waite-Smith tarot deck of 78 cards.' It clearly distinguishes itself from get_tarot_cards_id by covering the full deck rather than a single card, and from the post_tarot_* siblings by being a read/list endpoint. The scope and resource are unambiguous.

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 explicitly names the alternative GET /cards/{id} and says it provides full upright/reversed interpretations and keywords, implying this endpoint is for lightweight listing. It also states the intended use cases ('tarot reference libraries, card databases, learning applications'). It does not explicitly mention all siblings like post_tarot_draw, but their post/random nature is obvious enough; the main alternative is covered.

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 tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?