Skip to main content
Glama
astroway

astroway-mcp

Official
by astroway

Lenormand: Daily Cards

astroway_tarot_lenormand_daily
Read-onlyIdempotent

Generate a daily three-card Lenormand reading seeded by a specified date to provide focused guidance for the day.

Instructions

Daily three-card draw based on date seed.

[Group: Tarot: Lenormand] [Endpoint: POST /v1/tarot/lenormand/daily] [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.
dateNo

Output Schema

NameRequiredDescriptionDefault
dateNo
seedNo
drawnNo
spreadNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description contributes the 'date seed' determinism idea and the credit cost/endpoint, but says nothing about what the draw returns or whether omitting date defaults to today.

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 sentence is front-loaded and waste-free. The bracketed group/endpoint/cost lines are operational metadata rather than descriptive padding, so they are defensible but not free.

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?

With a rich annotation set and an output schema present, the description needn't explain return values. However, it omits the one thing an agent still needs: what happens when date is omitted and why to choose this over other Lenormand draws.

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

Parameters3/5

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

Schema coverage is 50%: 'art' is well documented in the schema, while 'date' only has a regex pattern with no explanation. The description's 'based on date seed' hints at the date parameter's role but doesn't clarify default behavior when it is omitted, which matters since no parameters are required.

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 names a specific verb and resource: a daily three-card Lenormand draw seeded by date. That distinguishes it from generic draws like astroway_tarot_lenormand_draw_three_card, though it never names that sibling or states the distinction explicitly.

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 guidance on when to use this tool versus the other Lenormand spread tools in the sibling list. The only implied usage cue is the word 'daily'.

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