Tarot

Get Card

get_card

Read-onlyIdempotent

Looks up one card from the Pipeworx original tarot deck by its id (e.g. "major_00", "wands_01") or its exact name (e.g. "The Fool"). Returns both upright and reversed meanings as reference, plus keywords and the image description.

Input Schema

Name	Required	Description	Default
`name_short`	Yes	Card id ("major_00".."major_21", "wands_01".."pentacles_14") or exact card name (e.g. "The Fool", "Ace of Wands").

Output Schema

Name	Required	Description
`id`	No
`name`	No	Full name of the tarot card
`rank`	No
`suit`	No	Suit of the card (null for Major Arcana)
`arcana`	No
`number`	No
`source`	No
`element`	No
`rank_name`	No
`meaning_upright`	No
`keywords_upright`	No
`meaning_reversed`	No
`image_description`	No
`keywords_reversed`	No
`astrological_correspondence`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed24 schema fields changedNov 3, 2026

changedInput schema / examples

Previous value: -[
-  {
-    "name_short": "ar01"
-  },
-  {
-    "name_short": "wap01"
-  }
-]New value: +[
+  {
+    "name_short": "major_00"
+  },
+  {
+    "name_short": "wands_01"
+  }
+]

changedInput schema / properties / name_short / description

Previous value: -"The short name identifier of the card (e.g. \"ar01\", \"ar00\", \"wap01\", \"cup10\")."New value: +"Card id (\"major_00\"..\"major_21\", \"wands_01\"..\"pentacles_14\") or exact card name (e.g. \"The Fool\", \"Ace of Wands\")."

addedOutput schema / properties / arcana
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / astrological_correspondence

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

removedOutput schema / properties / desc

Removed value: -{
-  "description": "Detailed description of the card",
-  "type": "string"
-}

addedOutput schema / properties / element
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / id
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / image_description
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / keywords_reversed

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / keywords_upright

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

removedOutput schema / properties / meaning_rev

Removed value: -{
-  "description": "Reversed meaning of the card",
-  "type": "string"
-}

addedOutput schema / properties / meaning_reversed
```
Added value: +{
+  "type": "string"
+}
```

removedOutput schema / properties / meaning_up

Removed value: -{
-  "description": "Upright meaning of the card",
-  "type": "string"
-}

addedOutput schema / properties / meaning_upright
```
Added value: +{
+  "type": "string"
+}
```

removedOutput schema / properties / name_short

Removed value: -{
-  "description": "Short identifier for the card",
-  "type": "string"
-}

addedOutput schema / properties / number

Added value: +{
+  "type": [
+    "number",
+    "null"
+  ]
+}

addedOutput schema / properties / rank

Added value: +{
+  "type": [
+    "null",
+    "number"
+  ]
+}

addedOutput schema / properties / rank_name

Added value: +{
+  "type": [
+    "null",
+    "string"
+  ]
+}

addedOutput schema / properties / source
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / properties / suit / type

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

removedOutput schema / properties / type

Removed value: -{
-  "description": "Card type (e.g. Major Arcana, Minor Arcana)",
-  "type": "string"
-}

removedOutput schema / properties / value

Removed value: -{
-  "description": "Card value or number",
-  "type": "string"
-}

removedOutput schema / properties / value_int

Removed value: -{
-  "description": "Integer representation of card value",
-  "type": "number"
-}

removedOutput schema / required

Removed value: -[
-  "name",
-  "name_short",
-  "value",
-  "value_int",
-  "type",
-  "suit",
-  "meaning_up",
-  "meaning_rev",
-  "desc"
-]

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "desc": {
+      "description": "Detailed description of the card",
+      "type": "string"
+    },
+    "meaning_rev": {
+      "description": "Reversed meaning of the card",
+      "type": "string"
+    },
+    "meaning_up": {
+      "description": "Upright meaning of the card",
+      "type": "string"
+    },
+    "name": {
+      "description": "Full name of the tarot card",
+      "type": "string"
+    },
+    "name_short": {
+      "description": "Short identifier for the card",
+      "type": "string"
+    },
+    "suit": {
+      "description": "Suit of the card (null for Major Arcana)",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "type": {
+      "description": "Card type (e.g. Major Arcana, Minor Arcana)",
+      "type": "string"
+    },
+    "value": {
+      "description": "Card value or number",
+      "type": "string"
+    },
+    "value_int": {
+      "description": "Integer representation of card value",
+      "type": "number"
+    }
+  },
+  "required": [
+    "name",
+    "name_short",
+    "value",
+    "value_int",
+    "type",
+    "suit",
+    "meaning_up",
+    "meaning_rev",
+    "desc"
+  ],
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026

addedInput schema / examples

Added value: +[
+  {
+    "name_short": "ar01"
+  },
+  {
+    "name_short": "wap01"
+  }
+]

First observedApr 14, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive. The description adds useful context beyond them: it returns both upright and reversed meanings plus keywords and image description, which tells the agent what the payload contains. Lacking only error behavior for unknown ids.

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?

Two tightly packed sentences with no waste: purpose and accepted keys first, then return contents. Front-loaded and readable.

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?

For a one-param lookup tool with full schema coverage, annotations, and an output schema, the description covers purpose, key formats, and return shape. Nothing an agent needs to call it correctly 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 coverage is 100%, so the schema documents name_short fully. The description adds value by giving examples of both accepted key forms (id like "major_00" and exact name like "The Fool"), reinforcing the dual-mode parameter beyond the schema text.

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?

States a specific verb (looks up), resource (one card from the Pipeworx tarot deck), and lookup keys with concrete id/name examples. It clearly distinguishes itself from search_cards, random_card, and draw_cards by being a single-card exact lookup.

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 makes clear this is for fetching exactly one known card by id or exact name. It does not explicitly name siblings like search_cards as the alternative when the key is unknown or partial, but the 'exact name' constraint implies the boundary reasonably well.

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

All Tarot 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.