Skip to main content
Glama
astroway

astroway-mcp

Official

Marseille — Career

tarot_marseille_draw_career
Read-onlyIdempotent

Draw a 4-card Tarot de Marseille spread to gain insight and guidance on career-related questions, helping you identify focus areas and navigate professional decisions.

Instructions

4-card career spread.

[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 readOnlyHint=true, idempotentHint=true. The description adds the number of cards (4) but does not disclose any additional behavioral traits (e.g., whether it returns a full reading, stores data, or has rate limits). With annotations covering safety, the description provides minimal extra transparency.

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 description is concise (two lines plus example). The group tag is useful for categorization. The example is helpful but could be separated for clarity. 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?

For a simple tarot draw with one parameter and good annotations, the description covers the basics. However, it does not explain the return format or what the tool outputs (e.g., card names, positions). Adding return context would improve completeness.

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 schema has one 'body' parameter described as 'Raw JSON body — see the example in the tool description'. The description provides an explicit example showing required fields (seed, question, allowReversed), which adds meaning beyond the minimal schema description. This compensates for the generic schema.

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 '4-card career spread' clearly states the verb (draw), resource (tarot cards), and scope (career). The group tag '[Group: Tarot — Marseille]' helps identify the deck. Among many sibling tarot draw tools, 'career' distinguishes it from love, spiritual, etc.

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?

The description indicates use for career questions but does not specify when not to use it or mention alternatives (e.g., other career tools like reports_career). No explicit exclusion criteria or comparison to siblings.

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