Skip to main content
Glama

Create team

create_team

Create a named scoreboard team on a Minecraft server, with an optional player-facing display name. Fails if the team already exists, preventing duplicate teams.

Instructions

Create a scoreboard team (fails if it already exists).

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": "create_team"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesTeam name (no spaces).
display_nameNoName shown to players; default: the internal name.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and idempotentHint=false; the description adds genuinely new behavioral context by disclosing the error behavior on name collision, which is exactly what the non-idempotent hint implies but doesn't spell out. It says nothing about the returned payload, but an output schema exists to cover that.

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?

A single short sentence with the resource first and the failure condition attached inline. There is no filler and nothing an agent must read past to reach the key facts.

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 simple two-parameter creation tool with rich annotations, full schema coverage, and an output schema, the definition covers purpose and failure mode adequately. The only minor gap is that it doesn't state the scope of the team (e.g., whether it is namespaced to the server/scoreboard), which could matter before calling.

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 both 'name' (pattern, length, no-spaces rule) and 'display_name' (defaulting to the internal name) are already fully documented. The description adds no meaning beyond the schema, 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?

The description uses a specific verb+resource ('Create a scoreboard team'), which is enough to distinguish it from siblings like create_objective, create_bossbar, and remove_team. It stops short of an explicit differentiation statement, but the resource is unambiguous.

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?

The parenthetical '(fails if it already exists)' gives an important precondition an agent must check before calling, which is more than nothing. However, it offers no guidance on when to reach for this versus update_team_members or set_team_option, and no prerequisites are stated.

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