Skip to main content
Glama

Remove team

remove_team
DestructiveIdempotent

Deletes a scoreboard team and leaves its members teamless.

Instructions

Delete a scoreboard team; its members become teamless.

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

Input Schema

NameRequiredDescriptionDefault
nameYesTeam name (no spaces).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is fully covered. The description's one value-add is the consequence 'its members become teamless', which annotations cannot express. It does not say what happens to team-referencing objectives/options or how a missing team is handled, so it is only a partial step beyond the annotations.

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 clause-semicolon-clause sentence with zero preamble: the action is front-loaded and the side effect follows. Nothing could be removed without losing information.

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 one-parameter destructive tool with an output schema provided, the definition covers what is destroyed and the effect on members, which is what an agent most needs before calling. Missing only edge-case behavior (nonexistent team, team-referencing objectives), a minor gap given annotation coverage.

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%: the single 'name' parameter already documents the no-spaces pattern, length bounds, and required status. The description adds no additional meaning about how the name is matched (case sensitivity, exactness), so the 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?

The description pairs a specific verb ('Delete') with a specific resource ('scoreboard team'), so an agent can distinguish it from remove_objective, remove_bossbar, and remove_entity without reading schemas. It does not explicitly name what it is not, but the resource noun alone is differentiating enough.

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: 'Delete a scoreboard team' tells the agent this is the removal counterpart to create_team, but there is no explicit when-to-use, no prerequisite (e.g., team must exist), and no mention of update_team_members as the alternative for adjusting membership without deleting the team.

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