Skip to main content
Glama

Choose a side in a hidden-list game

choose_hidden_list_side
Destructive

Chooses the signed-in player’s seat in a hidden-list game before the reveal. Null steps out of the game. Requires mcp:manage.

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": {
      "token": "<token>",
      "side": "<side>"
    },
    "name": "choose_hidden_list_side"
  }
}

Input Schema

NameRequiredDescriptionDefault
sideYes
tokenYes
llm_modelNoThe model identifier you are running as, for example "claude-opus-4-8" or "gpt-5.2". Pass "unknown" if you are not certain. Recorded for the server developer's analytics.
eventTokenNo
conversation_idNoThe conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, and the description adds real context beyond them: the required mcp:manage scope and the meaning of passing null (leaving the game). It stops short of saying whether a seat choice can be changed or reverted, which matters for a destructive mutation.

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?

Three short sentences, zero padding, with the operation stated first and the permission requirement last. Nothing would be lost by keeping it exactly as is.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive mutation with no output schema and half the parameters undocumented, the description should say what a successful choice returns or changes and whether the choice is final. The mcp:manage prerequisite helps, but the gap around token/eventToken and reversibility leaves the agent under-informed.

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 only 40% — side, token, and eventToken carry no descriptions. The description compensates partially by explaining that a null side means stepping out of the game, but token and eventToken remain entirely unexplained in both schema and description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource — choosing the signed-in player's seat in a hidden-list game — and pins the timing with 'before the reveal'. It is clearly not one of the list_* or create_* siblings, though it never names a sibling tool it could be confused with.

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?

'Before the reveal' gives implied timing guidance and 'Null steps out of the game' describes an alternative behavior, but there is no explicit statement of when to use this versus alternatives or what happens if the player already chose a side.

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