Skip to main content
Glama
Sign In
The Fortuneteller's Hand

The Fortuneteller's Hand

by PistachioPony
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Draw Unclaimed Card

draw_unclaimed_card

Draw a card to generate new story material at the start of a scene or whenever the narrative needs fresh direction.

Instructions

Draw one card from the Fortuneteller's Hand deck to open or refuel a scene with new story material.

Call at the start of every new scene, and again mid-scene any time the
story genuinely needs new material rather than a yes/no answer — for a
yes/no question, use cast_omen instead. Read the returned phrase cold,
before narrating anything else; only afterward do you narrate the scene
forward and let its meaning land in the fiction.

Takes no parameters. Not idempotent: each call removes and returns a
different card from the shared, shuffled deck (auto-reshuffles when the
deck runs out). Returns a dict with rank, suit, suit_name, domain,
rank_meaning, and phrase.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.9/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 tool is not idempotent, removes a distinct card from a shared shuffled deck, auto-reshuffles when exhausted, and returns a dict with six specified fields. These are important behavioral details not available from readOnlyHint/destructiveHint alone.

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 front-loaded with the core purpose and every sentence adds needed guidance: when to use, when not to use, how to handle the phrase, non-idempotence, and return structure. It is longer than a one-liner, but the content is all operational and necessary.

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?

Because there is no output schema, the description fully covers the return value by listing the dict fields. It also explains deck behavior, reshuffling, and the intended narrative workflow, making the tool self-sufficient for an agent to invoke 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?

The tool takes no parameters, and the schema already reflects this with an empty properties object. The description explicitly confirms 'Takes no parameters,' so there is no parameter semantics gap to compensate for. Baseline 4 is appropriate for a zero-parameter tool.

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 tool's action: 'Draw one card from the Fortuneteller's Hand deck to open or refuel a scene with new story material.' It names the specific resource (Fortuneteller's Hand deck) and distinguishes its purpose from cast_omen, which is explicitly reserved for yes/no questions.

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 provides explicit invocation guidance: call at the start of every new scene, and mid-scene when the story needs new material. It also names the alternative for yes/no questions ('use cast_omen instead') and instructs the agent to read the returned phrase before narrating anything else.

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