Skip to main content
Glama

tarot_search

Read-onlyIdempotent

Search for a tarot card by name using queries like 'The Fool' or 'Ace of Cups' to identify and retrieve the matching card.

Instructions

Search for a specific tarot card by name.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "tarot_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesCard name (e.g. 'The Fool', 'Death', 'Ace of Cups')

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so safety and repeatability are fully covered structurally. The description adds nothing beyond that – no note on what a match returns (single card vs. list), whether matching is exact or fuzzy, or what happens on no match.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

A single front-loaded sentence with no padding. It is efficient, though its brevity is part of why gaps remain – it could afford one more clause on matching behavior.

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?

For a one-parameter read-only lookup with annotations and full schema coverage, this is minimally adequate. Missing: routing versus the two sibling tarot tools and match/no-match behavior, which are the only real decisions an agent must make here.

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% and the query parameter already carries examples ('The Fool', 'Death', 'Ace of Cups'). The description adds no matching-semantics detail (substring, case sensitivity, partial names) beyond the schema's examples, so baseline 3 applies.

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?

States a specific verb and resource ('Search for a specific tarot card by name'), so the operation is unambiguous. It does not distinguish itself from the sibling tools tarot_all_cards or tarot_draw, which also deal in tarot cards, so an agent gets no help picking among them.

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?

There is no when-to-use guidance and no mention of alternatives. The agent is not told when to search by name versus listing all cards (tarot_all_cards) or drawing a card (tarot_draw), which is the main ambiguity this tool has.

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

Deploy Server

Other Tools