Tarot

Search Cards

search_cards

Read-onlyIdempotent

Searches the Pipeworx original tarot deck by name, suit, or keyword — matches against card names, both orientations’ keywords and meanings, and suit.

Input Schema

Name	Required	Description	Default
`query`	Yes	Keyword or phrase to search for (e.g. "moon", "strength", "cups", "betrayal").

Output Schema

Name	Required	Description
`cards`	No	Array of matching tarot cards
`count`	No	Number of matching cards found
`source`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed24 schema fields changedNov 3, 2026

changedInput schema / properties / query / description

Previous value: -"Keyword or phrase to search for (e.g. \"moon\", \"strength\", \"cups\")."New value: +"Keyword or phrase to search for (e.g. \"moon\", \"strength\", \"cups\", \"betrayal\")."

addedOutput schema / properties / cards / items / properties / arcana
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / cards / items / properties / astrological_correspondence
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```

removedOutput schema / properties / cards / items / properties / desc

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

addedOutput schema / properties / cards / items / properties / element
```
Added value: +{
+  "type": [
+    "null",
+    "string"
+  ]
+}
```
addedOutput schema / properties / cards / items / properties / id
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / cards / items / properties / image_description
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / cards / items / properties / keywords_reversed

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

addedOutput schema / properties / cards / items / properties / keywords_upright

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

removedOutput schema / properties / cards / items / properties / meaning_rev

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

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

removedOutput schema / properties / cards / items / properties / meaning_up

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

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

removedOutput schema / properties / cards / items / properties / name_short

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

addedOutput schema / properties / cards / items / properties / number
```
Added value: +{
+  "type": [
+    "number",
+    "null"
+  ]
+}
```
addedOutput schema / properties / cards / items / properties / rank
```
Added value: +{
+  "type": [
+    "null",
+    "number"
+  ]
+}
```
addedOutput schema / properties / cards / items / properties / rank_name
```
Added value: +{
+  "type": [
+    "null",
+    "string"
+  ]
+}
```

changedOutput schema / properties / cards / items / properties / suit / type

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

removedOutput schema / properties / cards / items / properties / type

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

removedOutput schema / properties / cards / items / properties / value

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

removedOutput schema / properties / cards / items / properties / value_int

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

removedOutput schema / properties / cards / items / required

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

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

removedOutput schema / required

Removed value: -[
-  "count",
-  "cards"
-]

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "cards": {
+      "description": "Array of matching tarot cards",
+      "items": {
+        "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"
+      },
+      "type": "array"
+    },
+    "count": {
+      "description": "Number of matching cards found",
+      "type": "number"
+    }
+  },
+  "required": [
+    "count",
+    "cards"
+  ],
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026

addedInput schema / examples

Added value: +[
+  {
+    "query": "moon"
+  },
+  {
+    "query": "strength"
+  }
+]

First observedApr 14, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds useful search behavior: it matches against card names, both orientations' keywords and meanings, and suit. It does not discuss result limits or ranking, which is a minor gap.

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 one tight sentence with no filler. It front-loads the verb and resource and then specifies the matching scope, so every clause earns its place.

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 one required parameter, full schema coverage, rich annotations, and an output schema, the description is complete enough for correct invocation. The only omission is how many results are returned or how matches are ranked, but that is secondary given the output schema exists.

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 single query parameter is already documented with examples. The description adds meaning beyond the schema by clarifying what corpus is searched—names, both orientations' keywords and meanings, and suit—which helps an agent form better queries.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: searches the Pipeworx tarot deck. It also names the searchable fields (name, suit, keyword, meanings), so the tool's purpose is clear. It does not explicitly distinguish itself from siblings like get_card, random_card, or draw_cards, which keeps it from a 5.

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

Usage Guidelines3/5

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

Usage is implied: use this when you have a keyword or phrase to look up in the deck. The description does not say when to use search_cards versus get_card or random_card, nor does it state exclusions or alternatives. This is adequate but leaves routing to inference.

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.