Skip to main content
Glama
astroway

astroway-mcp

Official
by astroway

Marseille: Tirage du Héros (Hero's Journey)

astroway_tarot_marseille_draw_hero
Read-onlyIdempotent

Draw a six-card Marseille Tarot Hero’s Journey spread to map your objective, obstacles, key insight, and resolution for a question or situation.

Instructions

Authentic 6-card Hero's Journey spread from Jodorowsky/Costa "The Way of Tarot": Hero / Objective / two Obstacles / Key / Resolution.

[Group: Tarot: Marseille] [Endpoint: POST /v1/tarot/marseille/draw/hero] [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.1/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 cost (10 credits, Tier 1) and source authenticity, but omits behavioral details like randomness/seeding and how the question parameter affects the draw, which matter for a tool with seed and allowReversed parameters.

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?

One sentence plus compact metadata; front-loads the spread name and card layout with no wasted words.

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?

Output schema exists so return values need no explanation, and annotations cover safety. However, with 4 parameters at 25% description coverage, the description should clarify seed/question/allowReversed usage; it leaves those gaps.

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?

Schema description coverage is only 25% (only 'art' is described). The description adds no meaning for seed, question, or allowReversed, so it does not compensate for the low coverage.

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?

It names the specific spread (6-card Hero's Journey) and enumerates the card positions, which is more than a tautology. However, it does not explicitly differentiate from sibling spread tools like draw_three_card or draw_celtic_cross, so an agent cannot immediately tell why to choose this one.

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?

No when-to-use guidance, no alternatives, no exclusions. The description only describes the spread; it does not help an agent choose between this and the many other Marseille draw tools.

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