Skip to main content
Glama
astroway

astroway-mcp

Official
by astroway

Marseille: Tirage Réduit (Jodorowsky Reduced Cross)

astroway_tarot_marseille_draw_cross
Read-onlyIdempotent

Draws an authentic five-card Marseille Tarot cross spread: four Major Arcana positions plus a numerological synthesis card, answering a question via the Jodorowsky/Costa method.

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] [Endpoint: POST /v1/tarot/marseille/draw/cross] [Cost: 10 credits (Tier 1)]

Input Schema

NameRequiredDescriptionDefault
artNoCard art set, e.g. rws-1909, rws-restored, rws-vector. GET /v1/tarot/decks lists the sets per deck.
seedNo
questionNo
allowReversedNo

Output Schema

NameRequiredDescriptionDefault
seedNo
drawnNo
spreadNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuine value by disclosing the 10-credit cost, the endpoint, and the fact that the 5th card is a numerological reduction—behavioral details not present in structured fields. It stops short of explaining seed/idempotency or reversal behavior.

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?

The core definition is a single front-loaded sentence, with group/endpoint/cost as compact metadata tags. No wasted prose, though the bracketed metadata is slightly dense.

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

Completeness3/5

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

For a draw tool with an output schema and safety annotations, the description is adequate: it conveys what the spread is and its cost. It falls short on parameter meaning and spread-selection guidance, leaving real gaps an agent would have to guess.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With only 25% schema coverage, the description must compensate, but it says nothing about the four parameters (art, seed, question, allowReversed). The agent gets no meaning beyond what the schema already spells out, and half the parameters are undocumented in either location.

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?

States a specific verb (draw) and resource (a 5-card Marseille cross) and details the four positional archetypes plus a synthesis card, so the operation and output shape are legible. It does not explicitly contrast with siblings like draw_three_card or draw_celtic_cross, but the '5-card cross' identity is distinctive enough.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no indication of which alternative spread to pick over this one, and no prerequisites or exclusions. The agent must infer selection from the toolbox alone.

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

Deploy Server

Other Tools