Skip to main content
Glama
Sign In
tarot-mcp-server

tarot-mcp-server

by gokimedia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_all_cards

Retrieve all 78 tarot cards with their name, arcana, and suit for a complete deck reference in one simple call.

Instructions

List all 78 tarot cards with basic info (name, arcana, suit).

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_all_cards"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the burden and it does reasonably well: 'List' signals a read-only operation and the enumerated return content tells the agent exactly what to expect. It does not discuss safety traits explicitly, but for a zero-parameter list call there is little hidden behavior.

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?

One sentence delivers the scope and output fields without filler. The key information is front-loaded: list all cards, then the basic info contents.

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 parameterless list endpoint with no output schema, the description is complete: it names the full scope (78 cards) and the exact fields returned. Sibling names further clarify its catalog role.

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?

There are zero parameters, so the baseline is 4 and no parameter explanation is needed. The description correctly omits parameter details because none exist.

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 uses a specific verb ('List'), a precise resource ('all 78 tarot cards'), and states the returned fields (name, arcana, suit). This makes it clearly distinct from siblings like get_card_meaning or draw_random_card.

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?

Usage context is implied rather than stated: this is the catalog-level tool while siblings serve individual lookups, draws, and readings. It does not explicitly say when to choose this tool over the alternatives or provide negative guidance.

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