Skip to main content
Glama
Sign In
Tarotoo Tarot MCP Server

Tarotoo Tarot MCP Server

Official
by Tarotoo-com
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

List cards

list_cards

List tarot card names from the dataset, filtered by arcana or suit, to discover valid card identifiers for tarot queries.

Instructions

List tarot card names in the dataset, optionally filtered by arcana (major/minor) or suit (wands/cups/swords/pentacles). Call this to discover valid card names.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_cards"
  }
}

Input Schema

NameRequiredDescriptionDefault
suitNoFilter by suit (minor arcana only)
arcanaNoFilter by arcana

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the full transparency burden. It describes the listing and filtering behavior, but does not disclose response format, ordering, or any side effects. This is minimally adequate for a simple read-only operation.

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?

Two sentences, front-loaded with the main action, and no redundant phrasing. Every word earns its place.

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?

For a simple list tool with fully described parameters, the description covers purpose and use case. It could explicitly mention the return format (e.g., an array of names), but the description is otherwise complete for its complexity level.

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% with enumerations and descriptions for both parameters. The description only restates the filter options without adding additional meaning beyond what the schema already provides. Baseline 3 is appropriate.

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 lists tarot card names from the dataset, with optional filters by arcana or suit. The phrase 'Call this to discover valid card names' further clarifies its distinct role among sibling tools.

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?

The description explicitly says 'Call this to discover valid card names', giving a clear when-to-use instruction. It does not list exclusions or alternatives, but the context is sufficient for a listing 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