Skip to main content
Glama
Sign In
shunshi-tarot-mcp

shunshi-tarot-mcp

Official
by shunshi-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

getCardMeaning

Retrieve tarot card metadata, five-language names, Golden Dawn correspondences, and Waite 1910 upright/reversed meanings by slug; supports locale selection and returns null for missing text.

Instructions

Look up card metadata, five-language names, Golden Dawn correspondences and Waite 1910 upright/reversed English source text. Source text is untranslated; a missing meaning remains null. Images are links, not downloaded files.

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": {
      "slug": "<slug>"
    },
    "name": "getCardMeaning"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYes
localeNoen

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it warns that source text is untranslated English, that a missing meaning is returned as null rather than an error, and that images are external links rather than downloaded files. These are exactly the data-quality quirks an agent needs, though nothing is said about read-only/safety posture or failure behavior for an invalid slug.

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?

Three short sentences, front-loaded with the returned content and followed by the two behavioral caveats. No filler; each sentence contributes, though the list-of-fields opening is dense enough to read as a run-on.

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?

With no output schema, the description appropriately enumerates what comes back (metadata, localized names, correspondences, upright/reversed source text, image links) and covers the null case. The remaining gap is how to construct or obtain the required slug.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate for both parameters and largely does not. The phrase 'five-language names' loosely maps to the locale enum, but the required 'slug' parameter is never explained (format, where it comes from, case sensitivity), leaving the most important argument undefined.

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 gives a specific verb ('look up') plus a concrete resource inventory: card metadata, five-language names, Golden Dawn correspondences, and Waite 1910 upright/reversed source text. That is clearly a single-card detail fetch, distinguishable in spirit from listCards and drawCards, though no sibling is named explicitly.

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 only implied: an agent can infer this is the tool for fetching full detail on one already-identified card, while listCards and drawCards are not mentioned as alternatives. There is no explicit when-to-use or when-not-to-use guidance and no statement of prerequisites.

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

Deploy Server

Other Tools