Skip to main content
Glama

Players leave session

gameye_player_leave

Remove one or more players from a Gameye session and return the session's updated player count and IDs, with GAMEYE_API_TOKEN required to send the request.

Instructions

Remove one or more players from a Gameye session. Returns the session's player count and IDs as reported by the server. 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": {
      "session": "<session>",
      "players": "<players>"
    },
    "name": "gameye_player_leave"
  }
}

Input Schema

NameRequiredDescriptionDefault
dryRunNoReturn the exact request that would be sent, with the API token masked, and send nothing
playersYesOne or more player IDs
sessionYesSession ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.3

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare mutation and open-world behavior, but the description adds real value beyond them: it documents the return payload (player count and IDs as reported by the server), the GAMEYE_API_TOKEN requirement, and the fallback path where no request is sent without a token. It does not explain partial-failure semantics when some IDs are invalid, which is the main remaining gap.

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 sentences, front-loaded with the action, then the return value, then the auth precondition. No filler and nothing buried.

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 non-destructive mutation with full annotation coverage and no output schema, the description covers auth failure, dry-run, and return shape, which is nearly everything an agent needs. Only error/partial-success behavior for invalid player IDs is unaddressed.

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 100%, so all three parameters (session, players, dryRun) are already documented in the schema, including dryRun's token-masking behavior. The description adds no syntax or constraint detail beyond that, so 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?

A specific verb plus resource: "Remove one or more players from a Gameye session," and it names the outcome (returns player count and IDs). The inverse of the sibling gameye_player_join is obvious from the name and text, though the description never names that sibling explicitly, so it stops short of full differentiation.

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?

Usage is implied by the operation (kick players out of an existing session), and the auth precondition is stated. There is no explicit when-to-use vs. when-not guidance and no pointer to alternatives such as gameye_player_join or gameye_describe_session for verification.

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