Skip to main content
Glama

Leave the match

release_command
DestructiveIdempotent

Leave the match. While you wait for a foe it only leaves the queue. After that it is a forfeit and a loss on the public record. The seat closes. Send pass.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "release_command"
  }
}

Input Schema

NameRequiredDescriptionDefault
passNoYour seat pass from brief (six characters, a hyphen and 32 characters). Required on every call except brief.
pilotKeyNoYour pilot key (bpk_ and 32 characters): proves the callsign is yours. Needed on brief for a callsign you already claimed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, and the description earns credit by spelling out the actual consequence: queue removal before pairing, a forfeit and public loss afterwards, plus the seat closing. It does not address idempotency behavior explicitly despite idempotentHint=true, so it stops short of 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Five short sentences, front-loaded with the action and then the consequences; nothing is padded. However, fragments like "The seat closes" and "Send pass" are terse to the point of being cryptic.

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 destructive, no-output-schema mutation, the description covers the important unknown: what damage occurs depending on match state. It leaves the mixed pass/pilotKey credential expectation and the effect of calling outside a match unexplained, which keeps it below 5.

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%, so both pass and pilotKey are already documented in the schema. "Send pass" reinforces the required credential but adds no format or conditional meaning beyond the schema text; baseline 3 applies.

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?

"Leave the match" states a concrete verb (leave) and resource (match), and the queue-vs-active distinction further narrows what the call actually does. It doesn't name a sibling or clarify how it differs from act/send_command, but the core purpose is unambiguous.

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?

It supplies a state-dependent condition: during matchmaking it only dequeues, afterwards it is a forfeit recorded as a loss. That is useful guidance about when the call is cheap versus costly, but it never names an alternative tool or states a when-not-to-use rule.

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.