Skip to main content
Glama

Challenge a ruling

game_challenge

Challenges the last trivia ruling: three different AI models judge the player's answer against the clue, and the ruling flips only if at least two agree it should count. Once per clue. In a timeline game it re-checks the last placement against the years and says what was heard. 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_challenge"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe game's slug
play_idYesThe play id from start_story

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already state readOnlyHint=false, idempotentHint=false and destructiveHint=false, and the description is consistent with that by explaining that a majority vote can flip the ruling. It adds genuinely useful behavior beyond the structured fields: the 2-of-3 judging rule, the once-per-clue limit, timeline-specific re-checking, and the requirement to call it silently without narrating. It does not say what happens to the player when the challenge fails, which is the one remaining behavioral question.

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?

Front-loaded with the core mechanism, then constraints, then the invocation etiquette, which is a sensible order. The final sentence enumerates four forbidden filler phrases, which is longer than needed but is operationally specific rather than filler.

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 mutating, non-idempotent, no-output-schema tool, the description covers the resolution logic, the rate limit, the timeline variant, and the interaction style an agent must adopt. The main omission is the outcome when the challenge is rejected, which the agent would otherwise have to discover at runtime.

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 description coverage is 100% and both parameters (slug, play_id) are documented in the schema, so the baseline is 3. The description adds no extra meaning about the parameters themselves — no format hints or provenance beyond what the schema already says ('the play id from start_story').

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 specific verb (challenges) and a precisely scoped resource (the LAST trivia ruling), then explains the resolution mechanism: three AI models judge the answer and the ruling flips only on a 2-of-3 majority. An agent can tell exactly what this does and that it applies to the most recent ruling rather than an arbitrary one.

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?

Gives clear triggering context (a disputed trivia ruling, or a timeline placement being re-checked) and an explicit rate constraint: 'once per clue.' It does not name a sibling alternative or a when-not-to-call condition, but no sibling in the list offers a comparable challenge capability, so the gap is minor.

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