AstroWay Tarot

Lenormand: Grand Tableau

astroway_tarot_lenormand_draw_grand_tableau

Read-onlyIdempotent

Full 36-card layout: every card and house used.

[Group: Tarot: Lenormand] [Endpoint: POST /v1/tarot/lenormand/draw/grand-tableau] [Cost: 10 credits (Tier 1)]

Input Schema

Name	Required	Description
`art`	No	Card art set, e.g. rws-1909, rws-restored, rws-vector. GET /v1/tarot/decks lists the sets per deck.
`seed`	No
`fields`	No	Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response.
`question`	No
`precision`	No	Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.
`allowReversed`	No

Output Schema

Name	Required	Description	Default
`seed`	No
`drawn`	No
`spread`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 6, 2026

addedInput schema / properties / art

Added value: +{
+  "description": "Card art set, e.g. rws-1909, rws-restored, rws-vector. GET /v1/tarot/decks lists the sets per deck.",
+  "maxLength": 40,
+  "type": "string"
+}

First observedOct 5, 2026

TDQS

B3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false. The description adds the layout completeness and cost (10 credits), but says nothing about side effects, permissions, or output behavior beyond what annotations cover. It adds some billing context but not rich behavioral detail.

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?

Two content sentences plus bracketed endpoint/cost metadata. Front-loaded and free of redundancy, though the endpoint line is arguably not needed by an agent. Efficient overall.

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 not be explained. Annotations cover safety. However, for a tool sitting among many Lenormand spread variants, the description omits usage guidance and parameter clarification, leaving the agent to infer when this spread applies.

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 50% (art, fields, precision documented; seed, question, allowReversed not). The description mentions no parameters and does not compensate for the undocumented ones. An agent must rely on the schema alone for half the inputs.

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?

The description states the tool produces a full 36-card layout with every card and house used, which is a specific resource and scope. It implicitly distinguishes from partial Lenormand spreads, but does not name any sibling to make the distinction explicit.

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 prerequisites. The agent gets no help deciding between this and the many other Lenormand draw tools (three-card, nine-card square, relationship, etc.).

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

All AstroWay Tarot tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?