Skip to main content
Glama
astroway

astroway-mcp

Official

Marseille — Tirage Réduit (Jodorowsky Reduced Cross)

tarot_marseille_draw_cross
Read-onlyIdempotent

Draw a 5-card cross spread from the Marseille tarot based on Jodorowsky/Costa's system, including four Major Arcana positions and a synthesis card, to gain insight into a question.

Instructions

Authentic 5-card cross from Jodorowsky/Costa "The Way of Tarot" + Camoin ArtduTarot — 4 Major Arcana (consultant / external / higher / result) + 5th synthesis card (numerological sum reduced ≤22).

[Group: Tarot — Marseille]

Example request body: {"seed":12345,"question":"What should I focus on?","allowReversed":true}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYesRaw JSON body — see the example in the tool description for required fields
Behavior3/5

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

Annotations already mark it as read-only and idempotent. The description adds structural context (deck, positions) but no additional behavioral traits like authentication needs or rate limits.

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?

Description is very concise: one sentence explaining the spread, a group label, and an example. No redundant information, front-loaded with key details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema and the description does not explain return format or meaning of positions. Missing info on required body fields beyond the example. Significant gaps for a tarot reading tool.

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?

The input schema only defines a wrapper body object with no internal schema. The description provides an example request with seed, question, and allowReversed, but does not fully document all possible or required fields, leaving ambiguity.

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 clearly states it's a 5-card cross spread from Jodorowsky/Costa, specifying positions (consultant, external, higher, result) and a synthesis card. This distinguishes it from other tarot spreads like Celtic cross or three-card draws.

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?

No explicit guidance on when to use this spread vs alternatives. The description implies it's a general cross spread, but lacks differentiation from similar tools like draw_celtic_cross or draw_love.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/astroway/astroway-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server