Skip to main content
Glama

Asteria: Astrology & Tarot

Tarot card meaning

tarot_card
Read-onlyIdempotent

The meaning of one of the 78 tarot cards, by name (The Moon, Ace of Cups, Queen of Swords…, in the chosen language or English) or by number (0 The Fool … 21 The World, then 22–77 the minor arcana).

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": "tarot_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
cardNoCard number, 0–77.
nameNoCard name, e.g. The Moon, Ace of Cups.
languageNoLanguage of the readings: en, fr, es, pt-BR, ja or de (default en). Use the language of the conversation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so the safety profile is fully covered without the description. The text adds a useful domain fact (78 cards, 0–21 major then 22–77 minor arcana) but says nothing about what the 'meaning' payload contains or what happens when both name and card are supplied.

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?

A single sentence with the core purpose front-loaded and parenthetical examples used to illustrate both invocation modes without a wasted clause. Dense but every element (count, name examples, numbering scheme, language) carries information.

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 single-card lookup with full annotation coverage and no output schema, the description covers what an agent needs to call it correctly. The only omission is precedence when both optional parameters are supplied, which is a minor gap rather than a blocker.

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?

Schema coverage is 100%, so the baseline is 3, but the description genuinely adds meaning the schema lacks: it maps the numeric range onto major vs minor arcana (0–21, then 22–77) and states the language may be 'in the chosen language or English'. It does not clarify whether 'card' and 'name' are mutually exclusive alternatives or which wins, which is the remaining gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb+resource ('the meaning of one of the 78 tarot cards') and scopes it to a single card, which distinguishes it from draw/spread/yes-no siblings that produce readings rather than lookups. It does not name a sibling explicitly, but the lookup-vs-reading distinction is inferable.

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 is only implied: the description shows two access paths (by name or by number) which tells the agent how to invoke it, but there is no explicit 'use this when…' guidance and no stated exclusions relative to tarot_draw or tarot_yes_no. An agent can guess the intent, but nothing steers it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.