Skip to main content
Glama
astroway

astroway-mcp

Official

Lenormand — Daily Cards

tarot_lenormand_daily
Read-onlyIdempotent

Get a daily three-card tarot and Lenormand reading based on a specific date. Input a date to receive a seeded draw for guidance.

Instructions

Daily three-card draw based on date seed.

[Group: Tarot — Lenormand]

Example request body: {"date":"2026-05-04"}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYesDate YYYY-MM-DD
latitudeNoLatitude (some date-only endpoints accept location)
longitudeNoLongitude
timezoneOffsetNoUTC offset in hours
Behavior4/5

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

Annotations already indicate readOnly, non-destructive, and idempotent behavior. The description adds that the draw is 'based on date seed', implying deterministic output for the same date, which is useful context. No contradictions with annotations. However, it does not explain the effect of optional location parameters on the seed.

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 extremely concise: one sentence, a group tag, and an example. No wasted words, front-loaded with core information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite the tool's simplicity, there is no output schema, and the description does not explain the response format (e.g., card names, positions, interpretations). The optional location parameters are mentioned but their impact on the seeded draw is not clarified. More completeness is needed for an agent to use this effectively.

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 description coverage is 100%, so the schema already documents each parameter. The description adds only an example request body, which provides marginal extra value. With high schema coverage, baseline 3 is appropriate.

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 states 'Daily three-card draw based on date seed', which specifies the action (draw), resource (Lenormand cards), and distinguishing feature (seeded by date). The title and group tag reinforce that it is Lenormand, differentiating it from other tarot daily tools and other lenormand spread 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?

No guidance is provided on when to use this tool versus alternatives like other lenormand draws or other daily tarot tools. The description does not mention exclusions, prerequisites, or preferred use cases.

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