Skip to main content
Glama

AskY Tarot Reading

Card meaning

get_card_meaning
Read-onlyIdempotent

Returns AskY's published guide to one Tarot de Marseille card: keywords, what the card brings, the card reversed, the card in love and in work, a piece of advice, a question to reflect on, and a link to the card's page. Accepts the card's French, English or Spanish name (for example "Le Mat", "The Fool", "El Loco", "Ace of Cups", "Reina de Espadas") or a Major Arcana number from 0 to 21 (for example "13" or "XIII"). Covers all 78 cards. Use when someone asks what a card means. It does not interpret a spread; use get_tarot_reading for a reading.

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": {
      "card": "<card>"
    },
    "name": "get_card_meaning"
  }
}

Input Schema

NameRequiredDescriptionDefault
cardYesThe card's name in French, English or Spanish, or a Major Arcana number (0-21, Arabic or Roman).
langNoLanguage of the answer: "en" for English, "es" for Spanish. Use the language the person is writing in. Defaults to English.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds useful behavioral context beyond that: full 78-card coverage, accepted input forms, and the exact shape of the returned content. It stops short of mentioning rate limits or failure behavior for unrecognized card names, which keeps it from a 5.

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?

Front-loaded with the return payload, then input formats, then usage routing — a sensible order with no filler. It is on the longer side and the example list is somewhat dense, but every clause carries information an agent needs.

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

Completeness5/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 enumerating the returned fields. Combined with the input format guidance and the sibling routing, an agent has everything needed to select and invoke this tool correctly.

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 100%, so the baseline is 3, but the description earns more by giving concrete accepted-value examples across three languages and both numeral systems ("Le Mat", "The Fool", "El Loco", "13", "XIII"). It also implies the lang parameter should follow the user's writing language, adding intent beyond the enum.

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 ("Returns AskY's published guide to one Tarot de Marseille card") and enumerates exactly what the guide contains (keywords, reversed, love, work, advice, reflection question, link). It also explicitly distinguishes itself from get_tarot_reading, so an agent can separate it from siblings without opening a schema.

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

Usage Guidelines5/5

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

Gives an explicit trigger ("Use when someone asks what a card means") and an explicit exclusion with the correct alternative ("It does not interpret a spread; use get_tarot_reading for a reading"). Both the when and the when-not are stated.

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.

Resources