Skip to main content
Glama

Trivia clue

game_question

Opens one clue on a Plot Speaks trivia board and returns its text (not the answer). Category "final" opens the final once the board is clear. In a survey or letter game it deals the next question or puzzle: pass category "next" ("skip" gives the open one up; "no steal" closes a survey question after three strikes). In a timeline game it starts a round: pass the deck's name, then " for " and the players' names (the reply deals the first card); "next" repeats the open card. In Worms!, Yacht (and Pigs!) it sets up the game: pass "rules" for the how-to-play beats, or "players", the names and "and Wormbot" (Skipper in Yacht, Hambot in Pigs!) or "no CPU" ("play again" after a game). Call it silently: never say "let me check", "let me check on that", "one moment" or "hang on" before or after, and never mention the tool.

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>",
      "play_id": "<play_id>",
      "category": "<category>"
    },
    "name": "game_question"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe game's slug
valueNoThe value the player picked, e.g. 300
play_idYesThe play id from start_story
categoryYesThe category the player picked, or "final" ("next" in a survey or letter game; the deck's name in a timeline game; "rules" or "players Ann, Bob and Wormbot" in Worms!)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations declare non-idempotent and non-read-only but say nothing about sequencing or return content; the description fills that gap by stating the reply carries the clue text and not the answer, that a timeline "next" repeats the open card, that "no steal" closes a survey question after three strikes, and that the first timeline card is only dealt after players are named. It also imposes a real interaction constraint (call silently, no filler narration, never mention the tool). The only gap is the absence of any error or precondition behavior when the required play_id or category is invalid.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded and every clause carries information, but the body is a single dense paragraph of nested parentheticals that is hard to scan. It would read far better as a short bulleted list per game mode; length is defensible given four modes, but the structure is not.

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?

For a multi-mode, non-idempotent state-advancing tool with no output schema, the description covers what each mode does, what the reply contains, and how to invoke it quietly. It is nearly complete except for failure/precondition behavior and any mention of the value parameter.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds genuine semantics the schema only gestures at: the accepted category sentinels ("final", "next", "skip", "no steal", "rules", "players ... and Wormbot") and their per-game meaning, plus how player names are formatted in a timeline game. The value parameter is never explained in the description, which is the one remaining gap.

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?

"Opens one clue on a Plot Speaks trivia board and returns its text (not the answer)" states a specific verb, resource, and return scope, and the parenthetical distinguishes it from game_answer. It then names the concrete action per game variant (deal next question, start a round, set up the game), so the agent knows exactly what the call does in each mode.

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?

It gives explicit invocation conditions for each mode: "final" only when the board is clear, "next"/"skip"/"no steal" for survey and letter games, deck name in a timeline game, "rules" or "players" for setup, "play again" after a game. What it doesn't do is name sibling tools as alternatives (e.g., pointing to game_answer for answering), so the routing versus alternatives is implied rather than explicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources