Skip to main content
Glama

Cancel a lobby

cancel_lobby
DestructiveIdempotent

Use only when the user explicitly asks to cancel a lobby that has not started. Its invitation stops working and nobody can play it. A game in progress is stopped in Playloop instead. Reuse requestId for identical retries.

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": {
      "requestId": "<requestId>",
      "runId": "<runId>"
    },
    "name": "cancel_lobby"
  }
}

Input Schema

NameRequiredDescriptionDefault
runIdYesThe game ID (runId) returned by create_quiz, list_quizzes or get_quiz.
requestIdYesStable UUID for this intent. Reuse it with identical arguments after a lost response; use a new UUID for a different action.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already flag destructive=true, idempotent=true and readOnly=false, but the description adds concrete effect detail beyond that: the invitation is invalidated and participants can no longer play. It also explains the retry contract ('reuse requestId for identical retries'), which is genuine behavioral guidance. It stops short of stating permission requirements or whether a cancelled lobby can be restored, so not a 5.

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?

Four short sentences with no filler; the usage restriction and the scope condition are front-loaded, followed by effect and retry guidance in descending order of importance.

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?

An output schema exists, so return values need no explanation, and both parameters are documented in the schema. The description covers preconditions, side effects and retry behavior for a destructive mutation. Minor gaps remain around permissions and error conditions (e.g. cancelling an already-cancelled lobby).

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 their own descriptions, including the UUID format and the requestId reuse rule, so the schema does the heavy lifting. The description's closing sentence restates the requestId retry convention without adding new semantics, which is the expected baseline-3 case.

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 description names a specific verb and resource (cancel a lobby) and immediately narrows the scope to 'a lobby that has not started', which separates it from stopping a live game. The consequence sentence ('invitation stops working and nobody can play it') confirms exactly what the operation acts on.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit precondition ('only when the user explicitly asks') plus a state exclusion (lobby must not have started) and routes the in-progress case to a different path ('stopped in Playloop instead'). An agent has everything it needs to decide whether to call this or not.

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