Skip to main content
Glama
abdul-hamid-achik

Tarot MCP Server

list_all_cards

Retrieve a complete list of all 78 tarot cards, optionally filtered by major or minor arcana, to support tarot readings and interpretations.

Instructions

List all 78 tarot cards

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
arcanaNoFilter by arcana type (default: all)

Implementation Reference

  • The tool handler for 'list_all_cards' - extracts optional 'arcana' filter, calls tarotTools.getAllCards(), filters by arcana if needed, and returns a mapped list of card names, arcana, suit, number, and id.
    case 'list_all_cards': {
      const arcanaFilter = args.arcana as string || 'all';
      let cards = tarotTools.getAllCards();
      
      if (arcanaFilter !== 'all') {
        cards = cards.filter(c => c.arcana === arcanaFilter);
      }
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(cards.map(c => ({
              name: c.name,
              arcana: c.arcana,
              suit: c.suit,
              number: c.number,
              id: c.id
            })), null, 2),
          },
        ],
      };
    }
  • Input schema definition for the 'list_all_cards' tool - registers the tool with name, description, and an optional 'arcana' parameter (enum: major/minor/all).
    {
      name: 'list_all_cards',
      description: 'List all 78 tarot cards',
      inputSchema: {
        type: 'object',
        properties: {
          arcana: {
            type: 'string',
            enum: ['major', 'minor', 'all'],
            description: 'Filter by arcana type (default: all)',
          },
        },
      },
    },
  • src/index.ts:134-147 (registration)
    Tool registration within the TOOLS array - the 'list_all_cards' tool is registered as part of the MCP tool list with its name, description, and input schema.
    {
      name: 'list_all_cards',
      description: 'List all 78 tarot cards',
      inputSchema: {
        type: 'object',
        properties: {
          arcana: {
            type: 'string',
            enum: ['major', 'minor', 'all'],
            description: 'Filter by arcana type (default: all)',
          },
        },
      },
    },
  • The getAllCards() method on TarotTools class that returns all 78 tarot cards from the data source, called by the handler.
    getAllCards(): TarotCard[] {
      return allCards;
    }
  • The allCards data export - combines majorArcana and minorArcana arrays into the full collection of 78 tarot cards.
    export const allCards: TarotCard[] = [...majorArcana, ...minorArcana];
Behavior3/5

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

No annotations provided, so description carries full burden. It implies a read-only operation but does not explicitly state non-destructive behavior or other constraints. For a simple list, it is adequate but minimal.

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 concise sentence that front-loads the core purpose with no unnecessary words.

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

Completeness4/5

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

Given the tool's low complexity (simple listing with one optional parameter), the description is quite complete. It covers the main action and scope, though return format is not mentioned.

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% as the parameter 'arcana' is well-documented with enum values. The description adds no additional meaning beyond the schema, so baseline score 3 is appropriate.

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?

Description states 'List all 78 tarot cards' with a specific verb and resource, which is clear. However, it does not differentiate from sibling tools like 'search_cards' that may also list cards.

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 such as 'search_cards' or 'get_card_meaning'. The description only states what it does.

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