Skip to main content
Glama

deckofcards

by io.github.pipeworx-io

Draw Cards

draw_cards
Read-onlyIdempotent

Draw cards from a deck. Returns card details (suit, value) and remaining count. Specify count to draw multiple cards at once.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNoNumber of cards to draw. Defaults to 1.
deck_idYesThe deck ID returned by new_deck (e.g. "3p40paa87x90").

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
cardsYesArray of cards drawn
deck_idYesUnique identifier for the deck
remainingYesNumber of cards remaining in the deck

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: +[
+  {
+    "deck_id": "3p40paa87x90"
+  },
+  {
+    "count": 5,
+    "deck_id": "3p40paa87x90"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "cards": {
+      "description": "Array of cards drawn",
+      "items": {
+        "properties": {
+          "code": {
+            "description": "Card code (e.g., '2H', 'AS')",
+            "type": "string"
+          },
+          "image": {
+            "description": "URL to card image",
+            "type": "string"
+          },
+          "suit": {
+            "description": "Card suit (e.g., 'HEARTS', 'DIAMONDS')",
+            "type": "string"
+          },
+          "value": {
+            "description": "Card value (e.g., '2', 'ACE', 'KING')",
+            "type": "string"
+          }
+        },
+        "required": [
+          "code",
+          "value",
+          "suit",
+          "image"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "deck_id": {
+      "description": "Unique identifier for the deck",
+      "type": "string"
+    },
+    "remaining": {
+      "description": "Number of cards remaining in the deck",
+      "type": "number"
+    }
+  },
+  "required": [
+    "deck_id",
+    "cards",
+    "remaining"
+  ],
+  "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

B3.1/5.0
Behavior1/5

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

The description implies a state-changing operation (drawing cards removes them from the deck, changing the remaining count), but the annotations declare readOnlyHint=true. This is a direct contradiction, confusing the agent about whether the tool mutates state.

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 two concise sentences, front-loaded with the main verb and resource, and contains no filler. Every word adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple and has an output schema, so return values need not be explained. However, the description lacks usage context (e.g., requires a pre-existing deck) and is undermined by the readOnlyHint contradiction, making it only minimally complete.

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 covers both parameters with clear descriptions (count defaults to 1, deck_id from new_deck), achieving 100% coverage. The description adds no new parameter semantics beyond restating 'specify count to draw multiple cards'.

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 action ('Draw cards from a deck') and specifies the resource (a deck). It also notes the return value (card details and remaining count), distinguishing it from sibling tools like new_deck and shuffle_deck.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives, nor any prerequisites such as needing an existing deck. The description simply states what it does without contextual direction.

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

All deckofcards 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

B3.4/5.0
Disambiguation2/5

Multiple tools have overlapping purposes: ask_pipeworx and ask_pipeworx_beta are functionally identical (beta just has experimental routing), and the Polymarket suite (bet_research, polymarket_arbitrage, polymarket_edges, polymarket_edge_tracker, polymarket_fill_risk, polymarket_kalshi_spread) all revolve around prediction-market signal detection with unclear boundaries. Also ai_visibility_check and scan_competitor_ai_presence overlap heavily.

Naming Consistency2/5

Naming is a mix of verb-first (draw_cards, resolve_entity, discover_tools) and noun-first (entity_profile, new_deck, recent_alerts) styles, with inconsistent prefixes (pipeworx_feedback vs ask_pipeworx) and no unifying convention. Some tools are bare verbs (recall, remember), others are noun phrases (polymarket_edges).

Tool Count2/5

34 tools is excessive for a server named 'deckofcards' — only 3 tools relate to cards. Even as a general-purpose data/research server, 34 is on the high end and includes many near-duplicates (ask_pipeworx variants) and highly specialized tools that could be consolidated.

Completeness3/5

The research side is fairly complete (lookup, grounding, comparison, profiles, claim verification, memory, subscriptions), but the card-deck functionality is minimal (only create, draw, shuffle) and lacks any deck inspection or hand management. The server's scope is unclear, making it hard to assess true coverage.

Resources