Skip to main content
Glama

Asteria: Astrology & Tarot

Tarot reading (draw cards)

tarot_draw
Read-only

Draws 1 to 10 distinct cards at random from the 78-card tarot deck and returns the reading of each, in the order drawn: a card of the day, or a free spread whose positions you assign in that order.

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

Input Schema

NameRequiredDescriptionDefault
countNoHow many cards to draw (default 1).
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

A4.4/5.0
Behavior4/5

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

Beyond the annotations, the description discloses that cards are drawn randomly, are distinct, and are returned in the order drawn, which is important behavioral context for a non-idempotent tool. It does not describe output structure in detail, but it provides enough behavioral signal for correct invocation.

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?

The definition is a single well-structured sentence that front-loads the core action and follows with scope and use cases. Every clause contributes useful information without redundant wording.

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 two-parameter tool with annotations and no output schema, the description covers the key behavior: random distinct draw, deck size, ordering, and return of readings. It leaves some output detail implicit, such as whether readings include card names or interpretations, but is otherwise complete enough to call correctly.

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. The description adds meaningful semantics by clarifying that the count refers to distinct cards and that draw order corresponds to assigned spread positions; it does not add information about the language parameter beyond what the schema already provides.

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 states a specific verb and resource: drawing 1 to 10 distinct random cards from the 78-card tarot deck and returning each reading in draw order. It also names concrete use cases (card of the day or a free spread with user-assigned positions), which distinguishes it from a generic card lookup.

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?

It gives clear usage context: use this for a card of the day or a free spread where you assign positions in draw order. It does not explicitly name alternatives such as a predefined spread tool or when not to use this tool, so exclusions are absent.

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.