Skip to main content
Glama

Trivia answer

game_answer

Checks a player's answer to the open trivia clue, scores it and returns the ruling with the answer, or the next step of a stepped clue. In a survey game it checks an answer against the hidden board; in a letter game it takes a called letter or a solve attempt, in the player's own words; in a timeline game it takes where the open card goes (before X, between X and Y, at the end), in the player's own words; in Worms! it takes the face to keep ("the fours", "worms"), "roll again" or "stop", and "take" or "steal"; in Yacht it takes the dice to keep ("the threes", "keep 3 3 5", "keep all", "none", "reroll the one") or "score it", then the box ("full house", "fours", "chance") and a yes or no to "Take a zero?"; in Pigs! it takes "yes" (throw again) or "no" (bank). 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>",
      "answer": "<answer>"
    },
    "name": "game_answer"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe game's slug
answerYesWhat the player said, in their words
playerNoThe answering player's name, for the scores
play_idYesThe play id from start_story

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 already declare a non-readonly, non-idempotent, non-destructive mutation, and the description adds real behavioral context on top: the call scores the answer, returns the ruling together with the answer, and can return the next step of a stepped clue rather than a final verdict. It does not disclose what happens on an unparseable answer, whether scoring is exact-match or fuzzy, or whether a wrong answer ends the turn — gaps that matter for a repeated-call mutation tool.

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 first sentence is well front-loaded and the strongest part. The follow-on is a single dense semicolon chain compressed into one paragraph, which is hard to scan, and the closing style directive spends a full sentence listing four near-synonymous phrases to avoid, which could have been stated once.

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-game answer dispatcher with no output schema, the description does the necessary work of covering each game mode's expected input and hints at the return value. Remaining gaps are turn/phase preconditions and failure behavior, not the core input contract.

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 exceeds it for the most ambiguous parameter by spelling out that 'answer' is the player's own words and giving concrete accepted forms per game ('the fours', 'keep 3 3 5', 'between X and Y', 'roll again'). It adds nothing about slug, play_id or player, which the schema already describes.

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 opening sentence gives a specific verb chain and resource: 'Checks a player's answer to the open trivia clue, scores it and returns the ruling with the answer, or the next step of a stepped clue.' It goes further by enumerating, game by game, exactly what an 'answer' means (board guess, called letter, timeline placement, Worms! face, Yacht dice, Pigs! yes/no), which makes it clearly distinct from siblings like game_question or game_challenge.

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?

Usage is clear by implication: call it when a player has spoken their answer to the open clue, and the per-game enumeration tells the agent which game states route here. What is missing is explicit sequencing or exclusions — e.g. that the play must already be open, or which sibling to use instead when no clue is pending — so the agent must infer the precondition from the schema's 'play_id from start_story'.

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