Skip to main content
Glama

AskY Tarot Reading

Card of the day

get_card_of_the_day
Read-onlyIdempotent

Returns today's Tarot de Marseille card on AskY (the same card for everyone, changing each day, UK time): its name, the thought for the day, what the card brings, a picture address and a link to the card's page. Use when someone asks for the card of the day or a card for today. It does not draw a card for a personal question; use get_tarot_reading for that.

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": "get_card_of_the_day"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.5/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world and non-destructive behavior, so the safety profile is covered. The description adds genuinely new context the annotations cannot express: the card is identical for all users, rotates daily, and is anchored to UK time. It also enumerates the returned fields, which matters because there is no output schema. It stops short of noting any caching/staleness window, so not 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, zero filler: what it returns, when to use it, when to use the sibling instead. The most decision-relevant content (today's card, same for everyone, UK time) is front-loaded, and the exclusion is saved for the end.

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?

For a zero-required-parameter read tool with no output schema, the description covers the return contents, the refresh cadence and timezone, and the sibling boundary. An agent has everything it needs to call this correctly and to know when not to.

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 100% and the single 'lang' parameter already carries an enum with a per-value explanation and a stated default, so the schema does the heavy lifting. The description body adds nothing about language selection. Baseline 3 is appropriate here.

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 today's Tarot de Marseille card') plus the exact payload (name, thought for the day, picture address, page link). It also explicitly contrasts with the sibling get_tarot_reading, so an agent can separate the shared daily card from a personal draw without opening either 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 both a when-to-use ('someone asks for the card of the day or a card for today') and a when-not with the alternative named ('does not draw a card for a personal question; use get_tarot_reading for that'). No inference is required to route between the two tools.

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