Skip to main content
Glama

Update team

update_team
Destructive

Rename a team or changing its description / auto-assignment / icon and colour. Team names are stored in lowercase.

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

Input Schema

NameRequiredDescriptionDefault
iconNoIcon shown beside the team in the sidebar and assignment menus.
nameNo
team_idYes
icon_colorNoColour of the team icon.
descriptionNo
allow_auto_assignNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / icon
      Added value: +{
      +  "description": "Icon shown beside the team in the sidebar and assignment menus.",
      +  "enum": [
      +    "people-team",
      +    "headphones-sound-wave",
      +    "chat",
      +    "call",
      +    "mail",
      +    "tag",
      +    "credit-card-person",
      +    "content-settings",
      +    "lock-shield",
      +    "star-emphasis",
      +    "heart-handshake",
      +    "building-bank",
      +    "globe",
      +    "flash-on",
      +    "book",
      +    "wand",
      +    "settings",
      +    "alert",
      +    "calendar",
      +    "briefcase"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / icon_color
      Added value: +{
      +  "description": "Colour of the team icon.",
      +  "enum": [
      +    "slate",
      +    "blue",
      +    "green",
      +    "amber",
      +    "red",
      +    "violet",
      +    "teal",
      +    "pink"
      +  ],
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already signal a non-readonly, destructive mutation. The description adds useful behavior ('Team names are stored in lowercase') but does not explain partial-update semantics, permissions, or the effect of overwriting existing values, so it adds some but not rich context.

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?

The definition is brief and front-loads the update scope, then adds the lowercase note. Minor awkwardness in 'or changing' and the slash-separated field list keeps it from being fully polished.

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?

For a destructive update operation with no output schema, it adequately lists the mutable fields and one behavioral nuance. It leaves gaps around whether omitted fields are preserved, permission requirements, and the role of team_id, so it is viable but not complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With schema description coverage at only 33%, the description compensates well by naming five of the six parameters in plain language (name, description, auto-assignment, icon, colour) and adding the lowercase normalization rule for names. It still omits any mention of the required team_id, but the schema covers that requirement.

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 ('Rename...changing') and names the team resource plus the fields that can be changed: description, auto-assignment, icon, and colour. This distinguishes it from create/delete team tools, though it does not explicitly name which siblings it replaces.

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?

It implies use for modifying an existing team's metadata, which separates it from create_team/delete_team and member-management tools. However, it gives no explicit when-to-use/when-not guidance or prerequisites.

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