Skip to main content
Glama

Set team option

set_team_option
Idempotent

Change a Minecraft team setting such as color, friendly fire, display name, prefix, or suffix. Specify the team name, option, and new value to update it.

Instructions

Change a team setting such as its colour or friendly fire.

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>",
      "option": "<option>",
      "value": "<value>"
    },
    "name": "set_team_option"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesTeam name (no spaces).
valueYesNew value: true/false for friendlyfire and seefriendlyinvisibles; a colour name (red, blue, gold, dark_green, aqua, light_purple, ...) for color; text for displayname, prefix and suffix.
optionYesSetting to change.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare the mutation profile (readOnly=false, idempotent=true, destructive=false, openWorld=false), so the description is not carrying the full burden. It adds only illustrative examples of what can be changed, and says nothing about whether the team must pre-exist, whether changes persist, or what errors occur for an invalid option/value combination.

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 front-loaded sentence with no filler or redundancy. It is efficient, though arguably undersized for the amount of routing and behavior information a six-option mutation tool warrants.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Complexity is low (3 required params, no nested objects) and the schema plus annotations and output schema carry most of the load, so the description is close to adequate. The gap is the vague "such as" phrasing, which implies a partial list when the enum is actually closed and finite.

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%, and the schema itself documents the option enum, team-name constraints, and value typing in more detail than the description. The description adds no meaning beyond what the schema provides, so the baseline of 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?

States a specific verb and resource ("Change a team setting") that clearly separates it from create_team/remove_team/update_team_members. The two examples given (colour, friendly fire) are representative but incomplete relative to the six-value option enum, and there is no explicit differentiation from other set_* tools.

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 only implied: the verb "change" signals an existing team must be modified rather than created, but the description never states prerequisites, when to prefer this over create_team, or what happens for a nonexistent team. No alternatives or exclusions are named.

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