Skip to main content
Glama

Renew a lobby invitation

refresh_invitation
DestructiveIdempotent

Use when the user wants a fresh invitation for an existing editable lobby. Previous invitation links stop admitting new players. Returns the replacement link and expiry. Does not start play. 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": "refresh_invitation"
  }
}

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.3/5.0
Behavior5/5

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

The annotations flag destructiveHint=true and idempotentHint=true, and the description earns its keep by explaining exactly what is destroyed ('previous invitation links stop admitting new players') rather than restating the hint. It also confirms side-effect boundaries ('does not start play'), describes the response payload, and explains the idempotency mechanism via requestId reuse on retries.

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?

Five short sentences, each carrying distinct information: trigger condition, destructive effect, return value, non-effect, and retry semantics. The activation cue is front-loaded and there is no filler or repeated phrasing.

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

Completeness5/5

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

For a two-parameter mutation on a reissued credential, the description covers trigger, state requirement, consequence for existing links, response contents, and idempotent retry behavior. With an output schema present, additional return-value detail is unnecessary, and nothing an agent needs to call this safely is missing.

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 are already documented in the schema, including the requestId retry contract, so the description's retry sentence largely repeats existing structured data. It adds no new meaning about runId resolution beyond what the schema's description of create_quiz/list_quizzes/get_quiz already provides, which is the expected baseline here.

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?

The description defines the specific action (issue a fresh invitation) and constrains it to an 'existing editable lobby', so the agent knows the target resource and its required state. It stops short of naming any contrasting tool because no sibling offers an invitation operation, leaving the boundary with create_quiz implicitly handled by schema descriptions.

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?

'Use when the user wants a fresh invitation for an existing editable lobby' is an explicit activation condition, and 'Does not start play' rules out a plausible mistaken expectation. No alternative tool is named, so there is no when-not routing, but the positive context is unambiguous.

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