Skip to main content
Glama

tarot

by io.github.pipeworx-io
OverviewAdmin

Draw Cards

draw_cards
Read-onlyIdempotent

Draw a spread of 1–78 random tarot cards (pass count). Returns each card's name, short ID, suit, type, upright meaning, reversed meaning, and description.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYesNumber of cards to draw (1–78).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
cardsYesArray of drawn tarot cards
countYesNumber of cards drawn

Schema Changelog

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

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "count": 3
+  },
+  {
+    "count": 10
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "cards": {
+      "description": "Array of drawn 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 cards drawn",
+      "type": "number"
+    }
+  },
+  "required": [
+    "count",
+    "cards"
+  ],
+  "type": "object"
+}
  2. Changed2 schema fields changed
    • removedInput schema / examples
      Removed value: -[
-  {
-    "count": 3
-  },
-  {
-    "count": 10
-  }
-]
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "cards": {
-      "description": "Array of drawn 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 cards drawn",
-      "type": "number"
-    }
-  },
-  "required": [
-    "count",
-    "cards"
-  ],
-  "type": "object"
-}New value: +null
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "cards": {
+      "description": "Array of drawn 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 cards drawn",
+      "type": "number"
+    }
+  },
+  "required": [
+    "count",
+    "cards"
+  ],
+  "type": "object"
+}
  4. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "count": 3
+  },
+  {
+    "count": 10
+  }
+]
  5. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already provide readOnlyHint, destructiveHint, idempotentHint, and openWorldHint, covering the safety profile. The description adds that cards are random and returns a list of card details, but with an output schema present, those return fields are already documented. It does not contradict the annotations.

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 sentences with no wasted words. The action is front-loaded ('Draw a spread...'), followed by a compact list of return fields. Every sentence 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?

For a simple one-parameter tool with a rich output schema and comprehensive annotations, the description is almost complete. It includes the valid range and return fields. It does not clarify whether cards are drawn without replacement, but this is a minor gap for a tarot spread tool at this complexity level.

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?

Input schema has 100% description coverage: count is described as 'Number of cards to draw (1–78)'. The description's mention of '1–78' and 'pass count' adds no meaningful semantics beyond the schema, so baseline 3 is appropriate.

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 uses a specific verb ('draw') plus resource ('random tarot cards') and clearly scopes the operation ('1–78'). It distinguishes from siblings like get_card or random_card by indicating a spread of cards with a count parameter.

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 clearly implies usage for drawing a random spread of tarot cards, giving context on when to use it. It does not explicitly state when not to use it or mention alternatives, but the purpose is self-evident and the operation is straightforward.

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

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

Resources