Skip to main content
Glama

Tarot Draw

by io.github.pipeworx-io

Tarot Draw Pull

tarot_draw_pull
Read-onlyIdempotent

Draw a tarot card from the 78-card deck. Interprets it for your situation. Accuracy not guaranteed. Refunds not available.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
spreadNoCard spread type
questionNoYour question for the cards. Optional. The cards do not care.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
cardNoThe name of the drawn tarot card
adviceNo
warningNo
questionNo
orientationNo
generated_atNo
interpretationNo

Schema Changelog

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

  1. Changed1 schema field changed
    • changedOutput schema / properties / warning / type
      Previous value: -"null"New value: +[
+  "string",
+  "null"
+]
  2. Changed11 schema fields changed
    • addedOutput schema / properties / advice
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / card / properties
      Added value: +{
+  "arcana": {
+    "type": "string"
+  },
+  "keywords": {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "name": {
+    "type": "string"
+  },
+  "number": {
+    "type": "number"
+  }
+}
    • changedOutput schema / properties / card / type
      Previous value: -"string"New value: +"object"
    • addedOutput schema / properties / generated_at
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / interpretation
      Added value: +{
+  "type": "string"
+}
    • removedOutput schema / properties / meaning
      Removed value: -{
-  "description": "Interpretation of the card for the given question",
-  "type": "string"
-}
    • removedOutput schema / properties / number
      Removed value: -{
-  "description": "The number or position of the card in its suit",
-  "type": "integer"
-}
    • addedOutput schema / properties / orientation
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / question
      Added value: +{
+  "type": "string"
+}
    • removedOutput schema / properties / suit
      Removed value: -{
-  "description": "The suit of the card (Major Arcana, Cups, Wands, Swords, Pentacles)",
-  "type": "string"
-}
    • addedOutput schema / properties / warning
      Added value: +{
+  "type": "null"
+}
  3. Added
  4. Removed
  5. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive nature. The description adds valuable behavioral context: 'Accuracy not guaranteed. Refunds not available.' and mentions the 78-card deck. No contradictions 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with purpose, followed by necessary disclaimers. Zero fluff; every sentence earns its place.

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?

Given full annotation coverage, a complete parameter schema, and the presence of an output schema (not shown but signaled), the description sufficiently covers all needed context for a simple tarot draw tool.

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?

Schema description coverage is 100% for both parameters. The description does not add significant new meaning beyond the schema's parameter descriptions; it only adds a touch of character ('The cards do not care'). 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 clearly states the verb ('Draw a tarot card' and 'Interprets') and the resource ('from the 78-card deck'). It distinguishes this tool from all siblings, none of which are tarot-related.

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?

While it does not explicitly state when to use this tool, the disclaimer 'Accuracy not guaranteed' implies it is for entertainment/divination, not factual decisions. No sibling tools exist as alternatives, so guidance is adequate but not explicit.

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

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

A3.7/5.0
Disambiguation2/5

Multiple tool families have unclear boundaries: ask_pipeworx and ask_pipeworx_beta are explicitly identical right now, suggest_questions and discover_tools are near-duplicates, and ai_visibility_check is a subset of scan_competitor_ai_presence. The five polymarket_* tools are heavily overlapping in purpose and rely on long descriptions to distinguish them, which an agent must read carefully to avoid misselection.

Naming Consistency3/5

All names are lowercase snake_case and there are helpful prefixes (polymarket_*, ask_pipeworx_*, pipeworx_*), but the verb/noun ordering is inconsistent: verb-first names (generate_llms_txt, resolve_entity, scan_dependency) sit alongside noun-first names (bet_research, entity_profile, recent_changes) and bare verbs (forget, recall, remember). Sub-families are internally consistent, but the set as a whole follows no single convention.

Tool Count2/5

32 tools is over the 'too many' threshold, and the scope is a grab-bag rather than a focused server: data research, prediction-market analysis, npm dependency checks, llms.txt generation, memory utilities, subscriptions, and exactly one tarot tool. The server is named 'Tarot Draw' yet 31 of 32 tools serve a completely different purpose, making the count wildly mismatched to the apparent identity.

Completeness2/5

For the inferred Pipeworx data/prediction-market domain the coverage is genuinely deep — ask/grounded/deep research, entity resolution, profiles, comparisons, validation, subscriptions, alerts, edge tracking, and arbitrage all exist. But for the stated purpose ('Tarot Draw'), the surface is one draw tool with no deck details, spreads, reading history, or reversal support, and the data tools' domain is so diffuse that an agent cannot rely on the set forming a coherent workflow.

Resources