Skip to main content
Glama

team_close

Close a team by marking it completed and setting all busy agents offline once its mission is fully done; requires a team ID or name and cannot be auto-resolved.

Instructions

Close (complete) a team — sets team status to completed and marks all busy agents as offline.

Use this when the team's mission is fully done. Members are not deleted, but their status is set to offline automatically.

team_id is REQUIRED — closing a team is not reversible from the tool side, so it never falls back to auto-resolving "the active team".

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "team_close"
  }
}

Input Schema

NameRequiredDescriptionDefault
team_idNoTeam ID or name (required — use team_list to find it)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.11.2

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations present, the description carries the full burden and does substantial work: it discloses the status transition, the automatic offline cascade to busy agents, non-deletion of members, and that the operation is not reversible from the tool side. What remains unstated is permission requirements and whether in-flight agent work is interrupted.

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?

Three short, front-loaded paragraphs: effect, when-to-use, parameter constraint. No filler and no repetition of the name or title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter mutation tool with an output schema present, nothing essential is missing — the destructive consequence, irreversibility, and required argument discipline are all covered, so an agent can call it correctly and safely.

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 genuine meaning beyond the schema: it explains why team_id is mandatory (irreversibility) and that it will never auto-resolve 'the active team'. This rationale is not derivable from the schema field description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (close) and resource (team) and immediately enumerates the concrete effects: status set to completed and busy agents marked offline. It also implicitly separates itself from team_delete by noting members are not deleted, so an agent can distinguish the two without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Gives an explicit trigger condition: 'Use this when the team's mission is fully done.' It also implies the boundary against team_delete by clarifying that members survive the call. It stops short of naming team_delete as the alternative or stating when not to close (e.g., work still running).

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

Deploy Server

Other Tools