Skip to main content
Glama

Asteria: Astrology & Tarot

Tarot spread reading

tarot_spread
Read-only

Lays out one of the app's tarot spreads (Single card, Question · Answer, Three cards, Lunation arc, Relationship mirror, Decision fork, Seven cards, Celtic Cross, Twelve houses) and draws a card for each position. Returns the spread, then for every position its name, what that position means and the card drawn with its reading. By default only the 22 major arcana are drawn, as in the app; deck "full" draws from all 78.

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": {
      "spread": "<spread>"
    },
    "name": "tarot_spread"
  }
}

Input Schema

NameRequiredDescriptionDefault
deckNomajors: the 22 major arcana (default); full: all 78 cards.
spreadYesWhich spread to lay out.
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
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), and the description adds real context beyond them: the default draws only the 22 major arcana "as in the app", the full deck is opt-in, and the return shape is spelled out position by position. The one meaningful omission is that idempotentHint=false is not explained — nothing says repeated calls draw fresh random cards.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with what the tool does before the deck caveat. The parenthetical spread list is long but each item is load-bearing, and no sentence is wasted, though the density makes it slightly harder to scan than a bulleted form would be.

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?

With no output schema, the description carries the return-value burden and does so adequately by describing per-position names, meanings and drawn cards. Nothing critical is missing for correct invocation; the residual gap is routing guidance against tarot_draw and a note that draws are non-deterministic.

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%, so the baseline is a 3, and the description stays close to that baseline. It does add value by translating enum slugs into human-readable spread names ("Question · Answer" for yes_no, "Lunation arc" for lunation_arc, "Twelve houses" for twelve_houses) and by restating the majors-by-default behavior, but language is left entirely to the schema.

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?

"Lays out one of the app's tarot spreads ... and draws a card for each position" is a specific verb plus resource, and the parenthetical enumerates every supported spread so the agent knows the full scope. It stops short of differentiating itself from siblings like tarot_draw or tarot_yes_no, even though the 'Single card' and 'Question · Answer' spreads visibly overlap with them.

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?

The description implies usage (it is the tool for multi-position spreads) and the spread names suggest their own contexts, but there is no explicit 'use this when... use tarot_draw instead when...' routing. With siblings like tarot_card, tarot_draw and tarot_yes_no in the catalog, an agent must infer the boundary itself.

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.