Skip to main content
Glama

Trivia board

game_board
Read-onlyIdempotent

Returns the current state of a Plot Speaks game in play, as text, without changing it. For trivia: the scores and the categories and values still on the board. For a survey or letter game: the scores, the open question or puzzle and what is revealed so far. For a timeline game: the line so far, lives and the open card. For Worms!: the tiles, stacks and open roll. Reads only; nothing is recorded. A play id that does not belong to that game returns an error, and a story that is not a game returns an error saying so. 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>"
    },
    "name": "game_board"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe game's slug or title, e.g. team-trivia
play_idYesThe play id start_story returned for this game, e.g. 3f2b8c1e-9d4a-4e7b-a1c2-5b6d7e8f9a0b

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / play_id / description
      Previous value: -"The play id from start_story"New value: +"The play id start_story returned for this game, e.g. 3f2b8c1e-9d4a-4e7b-a1c2-5b6d7e8f9a0b"
    • changedInput schema / properties / slug / description
      Previous value: -"The game's slug"New value: +"The game's slug or title, e.g. team-trivia"
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, yet the description still adds real value: 'nothing is recorded', the two explicit error conditions (play id not belonging to the game, story that is not a game), and the per-variant payload shape. It does not describe output format details such as ordering or empty-board representation, but the added behavioral context is substantial.

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?

The core is front-loaded and the per-variant enumeration is efficient and information-dense. The closing sentence forbidding 'let me check'/'hang on' phrasings is over-specified and padded relative to the single behavioral point it makes.

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 carries the burden of explaining return values and does so for every game type, plus the failure modes. It does not mention where slug/play_id come from (start_story appears only in the schema example), leaving a small gap for a first-time caller.

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

Parameters3/5

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

Schema coverage is 100% and both parameters carry descriptions with examples ('team-trivia', a UUID-shaped play id), so the schema already does the heavy lifting. The description only incidentally adds that the play id must belong to the named game (via the error clause); otherwise it adds no semantics beyond the schema.

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?

States a precise verb and resource ('Returns the current state of a Plot Speaks game in play') and then specifies the returned content per game variant (trivia, survey/letter, timeline, Worms!). This is far more specific than the bare name and distinguishes it from mutating siblings like roll or game_answer.

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 implied by 'read only, nothing is recorded' and by the error cases for an out-of-place play id or a non-game story, but no sibling alternative is ever named (e.g. game_question, roll, get_cue), so the agent must infer which read tool to pick. The 'call it silently' directive is a style rule, not selection guidance.

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