Skip to main content
Glama

Stop session

gameye_stop_session
DestructiveIdempotent

Terminate one Gameye session by its exact ID, disconnecting connected players and transitioning it to exited. Use dryRun to preview the request without sending it.

Instructions

Terminate one Gameye session by its exact ID (sends SIGTERM to the container). Any players connected to it are disconnected. The session transitions to 'draining' then 'shuttingdown' then 'exited'. There is no bulk or implicit stop: an empty, wildcard or list ID is refused. Pass dryRun=true to preview the request. Needs GAMEYE_API_TOKEN; without one, returns setup steps and sends nothing.

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": {
      "id": "<id>"
    },
    "name": "gameye_stop_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesExact ID of the one session to stop
dryRunNoReturn the exact request that would be sent, with the API token masked, and send nothing

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.3

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already flag destructive, idempotent and open-world, but the description adds real operational detail: SIGTERM delivery, player disconnection side effect, the draining → shuttingdown → exited lifecycle, and the auth failure mode that sends nothing. These are exactly the consequences an agent needs before a destructive call.

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 tight sentences, each carrying a distinct fact: action, side effect, state sequence, ID constraint, auth/dryRun behavior. Front-loaded with the operation and its blast radius; no filler.

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?

No output schema exists, yet the description covers the observable outcome (state transitions, dryRun preview) and the failure path (missing GAMEYE_API_TOKEN). Combined with 100% schema coverage, nothing needed to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description earns extra credit by clarifying that the id must be a single exact value and that empty/wildcard/list forms are rejected, plus the no-op guarantee for dryRun.

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 and resource with scope: "Terminate one Gameye session by its exact ID". The explicit singleness ("one", "exact ID", "no bulk or implicit stop") distinguishes it from list/describe/launch siblings without needing their schemas.

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 when-to-use context and important exclusions (empty, wildcard or list IDs are refused; no bulk stop), plus when to use dryRun for preview. It does not name an alternative sibling for bulk termination scenarios, which keeps it just short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.