Skip to main content
Glama
astroway

astroway-mcp

Official

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

tarot_marseille_draw_hero
Read-onlyIdempotent

Draw a 6-card Hero's Journey tarot spread for guidance on your path, revealing the hero, objective, obstacles, key, and resolution.

Instructions

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

[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
Behavior4/5

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

Annotations (readOnlyHint=true, etc.) already cover safety. The description adds value by specifying the spread's origin, card count, and positions. No contradictions with annotations. Behavioral context beyond annotations is minimal but acceptable given annotation coverage.

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?

The description is brief and front-loaded with the most important information (spread type, source, card positions). The group tag and example are clearly separated. Every sentence adds value without redundancy.

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?

The description omits any mention of the output format, which is important since no output schema is provided. It also does not clarify prerequisites or typical use cases beyond the spread itself. Adequate but not fully complete for an agent to understand the tool's full behavior.

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

Parameters4/5

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

The input schema defines a single 'body' object with no nested schema. The description compensates with an example request body showing required fields (seed, question, allowReversed). This is helpful but does not fully document all possible fields.

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 identifies the tool as a specific 6-card Hero's Journey spread from a well-known source (Jodorowsky/Costa). It lists the card positions (Hero, Objective, two Obstacles, Key, Resolution), making it highly distinct from sibling tarot tools.

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?

The description does not provide any guidance on when to use this spread versus other tarot spreads (e.g., Celtic Cross, love, career). No when-to-use, when-not-to-use, or alternative suggestions are given.

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