Skip to main content
Glama

tarot

by io.github.pipeworx-io
OverviewAdmin

Search Cards

search_cards
Read-onlyIdempotent

Search tarot cards by keyword — matches against card names and descriptions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesKeyword or phrase to search for (e.g. "moon", "strength", "cups").

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
cardsYesArray of matching tarot cards
countYesNumber of matching cards found

Schema Changelog

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

  1. Changed1 schema field changed
    • 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"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "query": "moon"
+  },
+  {
+    "query": "strength"
+  }
+]
  3. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds the behavioral detail that matching occurs against card names and descriptions, which is useful but not extensive. No contradiction.

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 a single, front-loaded sentence with no filler. It efficiently states the action, target, and matching criteria, earning its place entirely.

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 simple one-parameter search tool with a rich schema, complete annotations, and an output schema present, the description is adequately complete. It explains the purpose and matching scope without needing to detail return values or pagination.

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 schema already provides 100% coverage for the single parameter 'query' with a clear description and examples. The description adds the matching-fields context, but this is marginal. Baseline of 3 is appropriate since the schema does the heavy lifting.

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 ('Search') with a distinct resource ('tarot cards') and scope ('by keyword — matches against card names and descriptions'). It effectively distinguishes this tool from sibling tools like get_card, draw_cards, and random_card.

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 use when an agent needs to find cards by keyword or phrase, providing clear search context. However, it does not explicitly mention alternatives or when not to use this tool, though the search-focused language serves as a strong implicit guideline.

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