Skip to main content
Glama

Asteria: Astrology & Tarot

Tarot yes or no

tarot_yes_no
Read-only

Answers a yes-or-no question with the tarot, by the app's rule: major arcana are turned over one by one until a card decides (Judgement says yes, The Hanged Man says no, The Fool asks to rephrase the question). Returns the answer, the deciding card with its reading, and the cards turned before it, which tell why.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tarot_yes_no"
  }
}

Input Schema

NameRequiredDescriptionDefault
deckNomajors: the 22 major arcana (default); full: all 78 cards.
languageNoLanguage of the readings: en, fr, es, pt-BR, ja or de (default en). Use the language of the conversation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only cover the safety profile (read-only, not destructive, closed-world, non-idempotent); the description adds the genuinely useful part — the internal draw rule, which cards terminate the draw, and what is returned alongside the answer. It does not spell out that repeated calls yield different cards (consistent with idempotentHint=false) or what a 'rephrase' outcome looks like structurally.

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?

A single dense sentence, front-loaded with the purpose and the draw rule before the return contents. Every clause carries information, though the trailing 'which tell why' is slightly clipped and the sentence is long enough to be harder to skim than a two-sentence split would be.

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

Completeness4/5

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

There is no output schema, and the description compensates by describing the return payload (answer, deciding card with reading, preceding cards). The notable gap is that the tool takes no question parameter, so how the yes-or-no question is actually supplied is never addressed.

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% and both parameters are fully enumerated with defaults documented in-schema, so the schema carries the load. The description adds no meaning beyond it — no guidance on when to prefer 'full' over 'majors' or how language selection interacts with the reading.

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?

States a specific verb and resource ('Answers a yes-or-no question with the tarot') and then pins down the exact mechanism — major arcana turned one by one until Judgement/The Hanged Man/The Fool decides. This distinguishes it from generic siblings like tarot_draw and tarot_spread without needing to name them, since the yes/no decision rule is unique.

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?

Usage is clearly implied: this is the tool for a binary yes-or-no question, and the Fool case ('asks to rephrase') hints at what to do with unanswerable questions. But there is no explicit when-not-to-use guidance and no routing to tarot_spread or tarot_card for open-ended readings, leaving the agent to infer the boundary.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.