Skip to main content
Glama

Tarot MCP Server by RoxyAPI

by com.roxyapi

Celtic Cross Spread (10 cards)

post_tarot_spreads_celtic_cross
Read-only

Perform the legendary Celtic Cross spread - the most comprehensive and detailed tarot reading available, used by professional tarot readers worldwide for over a century. This 10-card layout reveals the complete picture of any situation through distinct positions: Present Situation (what is happening now), Challenge (obstacles crossing your path), Distant Past (root causes), Recent Past (recent influences), Best Outcome (potential positive result), Near Future (what is approaching in weeks ahead), Your Approach (your attitude and self-perception), External Influences (environment and other people impact), Hopes and Fears (your desires and anxieties), and Final Outcome (where everything is headed). Perfect for life-changing decisions, complex relationship questions, career transitions, spiritual guidance, and deep self-discovery. Ideal for professional tarot apps, life coaching platforms, spiritual wellness websites, and divination tools requiring authoritative comprehensive readings. Each card position provides layered insight combining traditional tarot wisdom with modern psychological interpretation for actionable guidance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
langNoResponse language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns English.en
seedNoOptional seed for reproducible results. The same seed always draws the same ten cards into the same Celtic Cross positions, which is what lets a reading be shared or re-rendered. Omit for a random draw.
compactNoSet true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.
questionNoOptional querent question to focus the Celtic Cross. It is echoed back on the reading and gives the ten positions their context. Omit for a general reading of the situation.

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already declare this as read-only and non-destructive, and the description adds meaningful behavioral context by detailing what the reading contains: ten distinct positions, each with an interpretation style, and querent question context. There is no contradiction, and the added position-level detail goes beyond the structured schema.

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

Conciseness2/5

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

The core information is front-loaded, but the description is overlong with marketing fluff: 'legendary', 'used by professional tarot readers worldwide for over a century', 'Perfect for ... life coaching platforms', 'Ideal for professional tarot apps', and other promotional language add no selection or invocation value. Several sentences can be trimmed without losing guidance.

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?

Given that the tool has zero required parameters and every parameter has detailed schema documentation, the description covers everything necessary to invoke it correctly. It could go further by describing the output shape, but is tool has no output schema and the description already enumerates the result positions, so the framing is complete enough.

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 all four parameters (lang, seed, compact, question) are already fully described. The description only reinforces the general purpose and position semantics but adds little new meaning beyond what the input schema 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 uses a specific verb-resource pairing: 'Perform the legendary Celtic Cross spread... This 10-card layout...' and goes on to enumerate all ten positions. This clearly distinguishes the tool from siblings like the three-card or love/career spreads, so an agent can tell exactly what it does.

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 gives explicit context for when to choose this tool: 'life-changing decisions, complex relationship questions, career transitions, spiritual guidance' and so on. It does not explicitly name alternatives or state when not to use it, but the use context is clear enough that a heuristic is provided.

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

All Tarot MCP Server by RoxyAPI toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: deck list/detail, daily draws, generic draws, four named spreads, custom spreads, and yes/no readings. Even the overlapping draw endpoints are distinguishable by their specific use cases.

Naming Consistency5/5

All tool names consistently follow a snake_case verb_tarot_resource pattern, which makes the toolset predictable and easy to navigate. The only minor oddity is get_tarot_cards_id, but it does not break the overall convention.

Tool Count5/5

Ten tools is an ideal size for a tarot API: two reference tools, one daily draw, one generic draw, four fixed spreads, one custom spread, and one yes/no tool. Each tool earns its place without overlap or bloat.

Completeness5/5

The surface covers the full tarot domain: browsing cards, retrieving detailed card interpretations, drawing cards, multiple popular spread types, custom spreads, and targeted yes/no guidance. There are no obvious dead ends or critical missing workflows.

Resources