Skip to main content
Glama
PistachioPony

The Fortuneteller's Hand

Cast Omen

cast_omen

Roll two ten-sided dice to answer a high-stakes yes/no question, returning a reading with direction and complication. Use when an outcome is unpredictable and carries real stakes.

Instructions

Cast an omen: roll two ten-sided dice (light vs dark, compared not summed) to answer a real yes/no question with real stakes.

Call whenever a scene reaches something no one can know in advance —
other hearts, hidden things, or the turn of luck — or when a player
claims an uncertain, high-stakes action simply succeeded. At least one
omen must be asked before a scene can close. Not for material that just
needs new story content rather than a yes/no answer — use
draw_unclaimed_card for that instead.

hope: a plain sentence naming the real stakes being asked about — what
the asker hopes is true (e.g. "I hope the guard doesn't notice me").

Not idempotent: each call rolls fresh dice and increments an internal
counter that alternates who narrates the result. Doesn't mutate any
other game state. Returns a dict describing the roll: on doubles,
{hope, light, dark, doubles: True, reading} — no answer, the Hand is
called instead (see call_the_hand). Otherwise {hope, light, dark,
doubles: False, direction, gap, texture, complication_rank,
complication_meaning, grounds_by} — direction and gap give the answer's
shape, grounds_by says whether the player or Claude narrates the
complication.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hopeYes
Behavior5/5

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

Discloses idempotency and state mutation beyond annotations: 'Not idempotent: each call rolls fresh dice and increments an internal counter that alternates who narrates the result. Doesn't mutate any other game state.' Also describes the doubles case where no answer is given and the Hand is called. Annotations only provide readOnlyHint:false and destructiveHint:false, so this adds significant value.

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?

Every sentence earns its place, covering purpose, usage, parameter, and behavior. The description is structured logically, front-loading the core mechanic, then usage rules, then parameter semantics, then return values. It is detailed but not redundant.

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?

With no output schema, the description fully details return values: 'Returns a dict describing the roll: on doubles, {hope, light, dark, doubles: True, reading} — no answer, the Hand is called instead (see call_the_hand). Otherwise {hope, light, dark, doubles: False, direction, gap, texture, complication_rank, complication_meaning, grounds_by}.' It also clarifies the meaning of key fields and side effects, making it complete for an agent.

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?

Schema coverage is 0%, so the description must fully explain parameters. It does: 'hope: a plain sentence naming the real stakes being asked about — what the asker hopes is true (e.g. "I hope the guard doesn't notice me").' This adds concrete meaning and an example, going beyond the schema's bare title.

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 explicitly states the tool's purpose with a specific verb and resource: 'Cast an omen: roll two ten-sided dice (light vs dark, compared not summed) to answer a real yes/no question with real stakes.' It clearly distinguishes from siblings by noting 'use draw_unclaimed_card for that instead' for non-yes/no content.

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?

Provides explicit when-to-use and when-not-to-use guidance: 'Call whenever a scene reaches something no one can know in advance — other hearts, hidden things, or the turn of luck — or when a player claims an uncertain, high-stakes action simply succeeded.' It also includes an exclusion and alternative: 'Not for material that just needs new story content rather than a yes/no answer — use draw_unclaimed_card for that instead.'

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/PistachioPony/learnMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server