Skip to main content
Glama
abdul-hamid-achik

Tarot MCP Server

search_cards

Find tarot cards by searching their names, keywords, and descriptions.

Instructions

Search for tarot cards by keyword

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query (searches names, keywords, and descriptions)

Implementation Reference

  • The actual searchCards method on the TarotTools class. It filters allCards by matching the query against card name, keywords, and description.
    searchCards(query: string): TarotCard[] {
      const lowerQuery = query.toLowerCase();
      return allCards.filter(card => 
        card.name.toLowerCase().includes(lowerQuery) ||
        card.keywords.some(k => k.toLowerCase().includes(lowerQuery)) ||
        card.description.toLowerCase().includes(lowerQuery)
      );
    }
  • src/index.ts:120-133 (registration)
    The tool registration/schema definition for 'search_cards' in the TOOLS array, including its name, description, and inputSchema with a required 'query' string parameter.
    {
      name: 'search_cards',
      description: 'Search for tarot cards by keyword',
      inputSchema: {
        type: 'object',
        properties: {
          query: {
            type: 'string',
            description: 'Search query (searches names, keywords, and descriptions)',
          },
        },
        required: ['query'],
      },
    },
  • The case handler in the CallToolRequestSchema switch that calls tarotTools.searchCards(query) and returns a mapped result.
    case 'search_cards': {
      const query = args.query as string;
      const cards = tarotTools.searchCards(query);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(cards.map(c => ({
              name: c.name,
              arcana: c.arcana,
              keywords: c.keywords,
              id: c.id
            })), null, 2),
          },
        ],
      };
    }
  • The TarotCard interface used as the return type for searchCards, defining fields like id, name, arcana, keywords, description, etc.
    export interface TarotCard {
      id: string;
      name: string;
      arcana: 'major' | 'minor';
      number?: number;
      suit?: 'wands' | 'cups' | 'swords' | 'pentacles';
      keywords: string[];
      uprightMeaning: string;
      reversedMeaning: string;
      description: string;
      element?: string;
      astrology?: string;
    }
Behavior2/5

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

No annotations provided, and the description lacks behavioral details such as whether results are ranked, limited, or paginated. The schema description for 'query' adds some info (searches names, keywords, descriptions), but the tool description itself is silent on behavior.

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?

The description is extremely concise at one sentence (5 words). While efficient, it could benefit from a bit more detail, but it is not overly verbose. It gets a high score for conciseness.

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

Completeness2/5

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

Given the lack of annotations and output schema, the description is too minimal for a search tool. It does not explain return format, result count, or any filtering behavior. The list of siblings suggests more comprehensive tools exist, making this one seem incomplete.

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 coverage is 100%, and the description adds no extra meaning beyond the schema parameter description. Baseline score of 3 is appropriate as the schema already documents the parameter semantics adequately.

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?

Description clearly states the tool searches for tarot cards by keyword, which distinguishes it from siblings like daily_card (specific card), draw_cards (random), and get_card_meaning (specific meaning). The verb 'search' and resource 'tarot cards' are explicit and unique.

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 on when to use this tool versus alternatives. For example, if the agent has a specific card name, get_card_meaning or list_all_cards might be more appropriate. The description does not provide any context for selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/abdul-hamid-achik/tarot-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server