Tarot MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| draw_cardsB | Draw a specified number of tarot cards |
| perform_readingB | Perform a tarot reading with a specific spread |
| interpret_readingB | Get a detailed interpretation of a tarot reading |
| get_card_meaningB | Get detailed information about a specific tarot card |
| list_spreadsA | List all available tarot spreads |
| get_spread_infoB | Get detailed information about a specific spread |
| daily_cardA | Draw a single card for daily guidance |
| search_cardsB | Search for tarot cards by keyword |
| list_all_cardsB | List all 78 tarot cards |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool has a clearly distinct purpose: daily card, drawing multiple cards, getting card meaning, spread info, interpreting reading, listing cards/spreads, performing spread, searching. No overlap or ambiguity.
Most tools follow a verb_noun pattern (draw_cards, get_card_meaning, etc.), but 'daily_card' breaks the pattern as a noun phrase. Still, the naming is mostly consistent and readable.
9 tools is well-scoped for a tarot reading server. Each tool serves a necessary function without being too many or too few.
Core tarot functionalities are covered: listing, searching, drawing, interpreting, and performing spreads. Missing custom spread creation or user history, but the surface is sufficient for typical use.