Skip to main content
Glama

Change team members

update_team_members
Idempotent

Manage Minecraft team membership by adding or removing players; joining a new team moves a player, ensuring each player is in only one team.

Instructions

Add and/or remove team members (a player can only be in one team; joining moves them).

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

Input Schema

NameRequiredDescriptionDefault
addNoPlayer names (or other entries).
nameYesTeam name (no spaces).
removeNoPlayer names (or other entries).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare non-read-only, non-destructive, idempotent behavior. The description adds a genuinely useful behavioral fact beyond them: a player can only belong to one team and joining moves them, which qualifies the 'non-destructive' signal since the player is silently removed from their prior team. It does not state what happens to unknown player names or to a nonexistent team.

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?

A single tight sentence with the core action front-loaded and the move constraint in a parenthetical. No wasted wording, though the parenthetical could be slightly better integrated.

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?

Annotations cover the safety profile and an output schema exists, so the description need not explain return values. It covers the one subtle behavioral wrinkle (cross-team moves); only edge cases like missing teams or invalid names are omitted.

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 the add, remove, and name parameters are fully documented in the schema itself. The description only implicitly maps to add/remove and adds no new semantics such as null-handling, empty-array behavior, or limits beyond what the schema states.

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 names a specific verb pair (add and/or remove) and resource (team members), making it clearly distinct from create_team, remove_team, and set_team_option. It stops short of explicitly naming those siblings, so differentiation is inferable rather than stated.

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?

Using it for membership changes is implied by 'add and/or remove,' and the parenthetical clarifies the move behavior. However, there is no explicit guidance on when to use this versus create_team/remove_team, nor any mention that the team must already exist (name is required).

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