Skip to main content
Glama
Sign In
Tarotoo Tarot MCP Server

Tarotoo Tarot MCP Server

Official
by Tarotoo-com
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Search cards

search_cards

Search all 78 tarot cards by theme, keyword, or topic. Get matching cards with keywords to interpret meanings.

Instructions

Search all 78 tarot cards by theme, keyword, or topic (e.g. "new beginnings", "heartbreak", "career success"). Searches names, keywords, and meaning texts. Returns matching cards with their keywords. Call this when you have a theme rather than a card 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": "search_cards"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (default 10)
queryYesSearch term or theme

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations provided, the description takes on the burden of explaining behavior. It states the search scope (names, keywords, meaning texts) and what is returned (matching cards with their keywords), adding clarity beyond the schema.

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?

Three sentences, front-loaded with the core purpose and an example. Every sentence adds value, with no filler or repetition.

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

Completeness5/5

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

For a simple search tool with no output schema, the description adequately explains what is searched and what is returned. It is complete enough for an agent to select and invoke the tool correctly.

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%, so both parameters are already well-documented. The description adds example queries and search scope but doesn't introduce new parameter semantics beyond the 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 the tool's function: search all 78 tarot cards by theme or keyword. It provides concrete examples and distinguishes the tool from sibling tools by specifying search by theme rather than card name.

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

Usage Guidelines4/5

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

Gives explicit guidance to use when a theme is available rather than a card name, implying get_card_meaning is for name-based lookups. It doesn't name alternatives explicitly but provides clear context for when to call this tool.

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