Skip to main content
Glama
Sign In

yarrow

by io.github.shaozhengkun123
OverviewDiscussionsAdmin

tarot_reading

Ask one real question through a single upright Waite-Smith Major Arcana card. Returns a direct calibrated answer first, the named card and bound Arthur Edward Waite 1910 source excerpt, a practical reality check, and one observable next step. No reversals, astrology, redraw loop, or guaranteed prediction. Daily quota is shared with completed divine and Two Lenses readings.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "question": "<question>"
    },
    "name": "tarot_reading"
  }
}

Input Schema

NameRequiredDescriptionDefault
seedNoDeterministic Tarot draw seed.
localeNoen
questionYesThe real question to reflect on.
device_idNoOptional opaque identifier for quota tracking. If omitted, IP-derived.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does disclose what the tool does NOT do (no reversals, astrology, redraw loop, guaranteed prediction) and the sharing quota, which is helpful. However, it doesn't state what happens to user data, API costs/limits beyond the quota-sharing hint, or whether this is a read-only operation. The behavioral expectations are partial.

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 a tight paragraph front-loaded with the core purpose and output structure, followed by constraints. Every clause earns its place — purpose, output format, disclaimers, quota. Slightly dense but efficient; could arguably be split into clearer sentences but remains readable and scannable.

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 tool has 4 parameters, no output schema, and no annotations, so the description must carry substantial weight. It covers output format, constraints, and quota well. However, it lacks detail on pricing/credits (day quota hints at it), whether the consultation is deterministic vs paid-per-call, response format details, or failure/edge cases like invalid questions. Adequate but leaves operational unknowns.

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?

Schema coverage is 75% (question, seed, locale, device_id described). The description reinforces the key 'question' parameter semantics ('one real question') and the single-card bound. The seed, locale, and device_id are adequately documented in the schema, so the description adds modest value by emphasizing the question qualifier ('real') and single-card constraint.

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 clearly states the verb+resource ('Ask one real question through a single upright Waite-Smith Major Arcana card') and details the output structure (direct answer, named card with Waite 1910 excerpt, reality check, next step). It differentiates from siblings by explicitly noting what it does NOT include (no reversals, astrology, redraw loop), though it doesn't name sibling alternatives directly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear context on when to use it — when a user has 'one real question' — and sets expectations about scope (single card, no redraw, no guaranteed prediction). It mentions the daily quota shared with divine and Two Lenses readings, which is useful operational guidance, though it doesn't explicitly name alternatives like cast_hexagram/tarot for other use cases.

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

All yarrow toolsInspect
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