tarot

Get Card

get_card

Read-onlyIdempotent

Get a specific tarot card by its short name identifier (e.g. "ar01" for The Magician, "ar00" for The Fool, "wap01" for Ace of Wands).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name_short`	Yes	The short name identifier of the card (e.g. "ar01", "ar00", "wap01", "cup10").

Output Schema

TableJSON Schema

Name	Required	Description
`desc`	Yes	Detailed description of the card
`name`	Yes	Full name of the tarot card
`suit`	Yes	Suit of the card (null for Major Arcana)
`type`	Yes	Card type (e.g. Major Arcana, Minor Arcana)
`value`	Yes	Card value or number
`value_int`	Yes	Integer representation of card value
`meaning_up`	Yes	Upright meaning of the card
`name_short`	Yes	Short identifier for the card
`meaning_rev`	Yes	Reversed meaning of the card

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "desc": {
+      "description": "Detailed description of the card",
+      "type": "string"
+    },
+    "meaning_rev": {
+      "description": "Reversed meaning of the card",
+      "type": "string"
+    },
+    "meaning_up": {
+      "description": "Upright meaning of the card",
+      "type": "string"
+    },
+    "name": {
+      "description": "Full name of the tarot card",
+      "type": "string"
+    },
+    "name_short": {
+      "description": "Short identifier for the card",
+      "type": "string"
+    },
+    "suit": {
+      "description": "Suit of the card (null for Major Arcana)",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "type": {
+      "description": "Card type (e.g. Major Arcana, Minor Arcana)",
+      "type": "string"
+    },
+    "value": {
+      "description": "Card value or number",
+      "type": "string"
+    },
+    "value_int": {
+      "description": "Integer representation of card value",
+      "type": "number"
+    }
+  },
+  "required": [
+    "name",
+    "name_short",
+    "value",
+    "value_int",
+    "type",
+    "suit",
+    "meaning_up",
+    "meaning_rev",
+    "desc"
+  ],
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026

addedInput schema / examples

Added value: +[
+  {
+    "name_short": "ar01"
+  },
+  {
+    "name_short": "wap01"
+  }
+]

First observedApr 14, 2026

TDQS

A4.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is well covered. The description adds minimal behavioral context beyond the identifier syntax, which is acceptable given the annotations.

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 a single, well-structured sentence with no filler. Examples are used efficiently to enhance understanding without redundancy.

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 simple read-only single-parameter tool with a rich output schema and comprehensive annotations, this description covers all necessary aspects. No gaps are evident.

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?

The schema fully documents name_short with examples, but the description adds valuable mappings (e.g., ar01=The Magician) that clarify the naming convention beyond the schema's generic description.

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 the action (get a specific tarot card), the resource (tarot card), and the mechanism (by its short name identifier). It provides concrete examples that distinguish it from sibling tools like random_card or search_cards.

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 emphasis on 'specific' and the requirement of a short name identifier imply this is for exact-ID lookups. No explicit alternatives are mentioned, but the context makes the intended usage clear without being misleading.

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

All tarot tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.