Skip to main content
Glama
PistachioPony

The Fortuneteller's Hand

by PistachioPony
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Local

Draw Cross Card

draw_cross_card

Draw a blind card from a chosen suit to fill a Motivation, Seek, Carry, or Ends slot in the character-creation cross, ensuring each suit and position is used only once.

Instructions

Draw one card, blind, into a position on the Sitting's cross — the four-drive character-creation spread built once at the start of every campaign.

Call once per drive during the Sitting, after the player has chosen a
suit for that drive: Motivation, then Seek, then Carry, then Ends, in
that order. Each of the four positions and each of the four suits can
only be used once each — calling this with a position or suit already
used raises ValueError. "Blind" means the card is drawn face-down from
the matching suit's own 13-card pile without looking; don't reveal its
phrase to the player until all four drives have a card.

suit: which of the four card suits (♥ Hearts, ♦ Diamonds, ♣ Clubs,
♠ Spades) the player chose for this drive — each suit represents a
different domain of meaning (love/loyalty, wealth/ambition,
labor/growth, death/conflict).
position: which of the four drives this card fills — Motivation, Seek,
Carry, or Ends.

Not idempotent: mutates the shared cross and removes a card from the
suit's pile. Returns the drawn card as a dict with rank, suit,
suit_name, domain, rank_meaning, and phrase.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
suitYes
positionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A5/5.0
Behavior5/5

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

Beyond the annotations, the description discloses that the operation is not idempotent, mutates the shared cross, removes a card from the suit's pile, returns a specific dict shape, and that the card's phrase should not be revealed until all four drives are filled. This is strong behavioral context.

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 dense but every sentence adds necessary context: purpose, invocation order, uniqueness constraints, blindness behavior, parameter meanings, mutation effects, and return shape. There is no filler or repetition of structured data.

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?

Given the tool has no output schema and only enum-based parameters, the description supplies all needed context: what the tool does, exactly when to call it, what parameters mean, what state changes occur, what errors arise, and what the returned dict contains. It is complete for safe invocation.

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

Parameters5/5

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

With 0% schema description coverage, the description fully compensates: it explains suit meanings and suits' names, defines position values as the four drives, and clarifies the semantic roles each suit represents. The parameters are entirely enriched beyond the bare enum values.

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 uses a specific verb and resource: 'Draw one card, blind, into a position on the Sitting's cross' and distinguishes this from sibling drawing tools by anchoring it to the four-drive character-creation spread. It clearly names what the tool does and the exact context.

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?

The description gives explicit when-to-use guidance: call once per drive after the player chooses a suit, and in the order Motivation, Seek, Carry, Ends. It also states when not to call it—each position and suit can only be used once, and a reused value raises ValueError.

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

Install Server

Other Tools