Skip to main content
Glama

Remove a player from a battle draft

remove_battle_player
Destructive

The creator removes a named player from a draft that has not started. This retires the current join link. Confirm the player and battle. Requires mcp:manage.

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": {
      "token": "<token>",
      "playerId": "<playerId>"
    },
    "name": "remove_battle_player"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYes
playerIdYes
llm_modelNoThe model identifier you are running as, for example "claude-opus-4-8" or "gpt-5.2". Pass "unknown" if you are not certain. Recorded for the server developer's analytics.
conversation_idNoThe conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already flag destructiveHint=true and openWorldHint=true, but the description adds meaningful context beyond them: the operation retires the current join link (a non-obvious side effect) and requires the mcp:manage scope. It does not explain reversibility or what happens to the removed player, so it is not exhaustive.

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?

Three short sentences with no filler, and the core action plus its precondition are front-loaded. The permission requirement ('Requires mcp:manage') is tacked on at the end rather than integrated, a minor structural quibble.

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, pre-start mutation with no output schema, the description covers actor, precondition, permission, and the join-link side effect, which is largely what an agent needs. It leaves out error behavior (e.g. if the draft has already started) and any confirmation of the result, which keeps it at a 4 rather than 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 50%: llm_model and conversation_id are self-documented, but token and playerId carry no schema description. The description only hints at them via 'Confirm the player and battle', which vaguely maps playerId to 'player' and token to 'battle' without stating the identifier format or where these values come from.

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 states a specific verb and resource ('removes a named player from a draft'), names the actor ('The creator'), and adds a scope qualifier ('that has not started'). An agent can distinguish it from a self-service action like withdraw_from_event, but no sibling is named 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 Guidelines4/5

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

It gives clear preconditions: only the creator, only drafts that have not started, and requires mcp:manage. 'Confirm the player and battle' sets an invocation expectation. There are no explicit exclusions or named alternatives (e.g. what to use once the battle has started), which keeps it below a 5.

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