Skip to main content
Glama

Update Agents in Team

update_agents_in_team
Destructive

Update Agents in Team. Set the team's members to exactly the agents in user_ids: agents not in the list are removed from the team, new ones are added Requires feature: team_management.

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>",
      "user_ids": "<user_ids>"
    },
    "name": "update_agents_in_team"
  }
}

Input Schema

NameRequiredDescriptionDefault
team_idYesThe ID of the team to be updated
user_idsYesIDs of users to be added to the team

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

The description explicitly discloses that agents absent from user_ids are removed, which is the crucial consequence for a destructive operation, and it states the required `team_management` feature flag. Annotations already cover the destructive hint, so this is solid added context; it does not describe side effects on removed agents' assignments or conversations.

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?

Two short sentences, front-loaded with the replacement semantics and the prerequisite, with no filler. The bold feature note is compact and useful.

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 two-parameter mutation with full schema coverage and rich annotations, the definition supplies the one thing structured fields omit: replacement rather than additive semantics. Missing only secondary detail such as whether removed agents must exist or what happens to their open work.

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 100%, so the baseline is 3, but the description adds real meaning: it corrects the schema's misleading 'users to be added' phrasing by establishing that user_ids is an authoritative full set whose complement is removed. That resolves a genuine ambiguity an agent would otherwise get wrong.

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 goes beyond the title by naming the resource (team membership) and the exact semantics: membership is replaced, not merged. It is clear enough to distinguish from single-member add/remove siblings, though it does not name them explicitly.

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 through the 'exactly' semantics; an agent can infer this is the bulk-replace call rather than add_team_member or remove_team_member, but no when-to-use or when-not-to-use guidance is stated. Context is clear, exclusions are absent.

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