Skip to main content
Glama

Coline

Update a team

update_team
DestructiveIdempotent

Renames a team or changes its description or icon.

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

Input Schema

NameRequiredDescriptionDefault
iconNoAn emoji.
nameNo
teamIdYesTeam id from list_teams.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
descriptionNo

Output Schema

NameRequiredDescriptionDefault
teamYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true and idempotentHint=true, so the safety profile is covered structurally. The description adds no behavioral context beyond restating the mutable fields: it does not say that renaming is destructive (breaks references, may notify members), whether partial updates leave other fields untouched, or what permissions are needed.

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 mutable fields front-loaded and no wasted wording. It is perhaps too terse for a destructive mutation, but it is appropriately sized and easy to scan.

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?

With five parameters, two required and an output schema available, the basics are covered. However, the description never states whether at least one of name/description/icon must be provided for the call to do anything, nor that unspecified fields are left unchanged — a real gap for a partial-update tool.

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?

Schema coverage is 60%, with name/description lacking descriptions, and the description usefully identifies which three fields are editable, mapping to the optional parameters. It stops short of format guidance (emoji constraints, whether at least one field must be supplied), which the schema only partially covers via maxLength.

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-plus-resource ('Renames a team') and enumerates the mutable fields (name, description, icon), so an agent knows exactly what operation it performs. It does not differentiate itself from siblings such as archive_team or create_team, but the mutation scope 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no prerequisites (permissions or role requirements), and no pointer to alternatives like archive_team or update_team_member_role. The agent must infer from the sentence alone that this is the tool for renaming or re-describing an existing team.

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