Skip to main content
Glama
abdul-hamid-achik

Tarot MCP Server

daily_card

Draw one tarot card each day to receive straightforward guidance and focus for your day.

Instructions

Draw a single card for daily guidance

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The `getDailyCard()` method in TarotTools class - draws a single card by calling `this.drawCards(1)` and returns the first card. This is the core handler/logic for the daily_card tool.
    getDailyCard(): DrawCard {
      const cards = this.drawCards(1);
      return cards[0];
    }
  • The `DrawCard` interface defines the return type of getDailyCard() - it contains a `TarotCard`, `position`, and `isReversed` flag.
    export interface DrawCard {
      card: TarotCard;
      position: string;
      isReversed: boolean;
    }
  • src/index.ts:112-119 (registration)
    The tool registration in the TOOLS array - defines name 'daily_card', description 'Draw a single card for daily guidance', and empty inputSchema (no params required).
    {
      name: 'daily_card',
      description: 'Draw a single card for daily guidance',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • The request handler case for 'daily_card' - calls `tarotTools.getDailyCard()` and returns the card serialized as JSON text.
    case 'daily_card': {
      const card = tarotTools.getDailyCard();
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(card, null, 2),
          },
        ],
      };
    }
Behavior2/5

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

With no annotations, the description carries full burden. It only states 'draw a single card' without disclosing any behavioral traits like randomness, side effects, or authorization needs. Minimal disclosure.

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?

Extremely concise: one phrase with no wasted words. Front-loaded purpose.

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?

Given no parameters, no output schema, and no annotations, the description is minimal but adequate for a simple tool. However, it could usefully indicate whether the draw is random or from a specific set.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

No parameters exist, so schema coverage is 100%. The description adds meaning by specifying 'for daily guidance,' which provides context beyond the empty schema.

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 it draws a single card for daily guidance, which is a specific verb+resource combination. It distinguishes from siblings like 'draw_cards' (likely multiple) and 'perform_reading' (more complex).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for daily guidance but provides no explicit when/when-not guidance or alternatives. It lacks exclusions or comparisons to sibling tools.

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