Skip to main content
Glama

Coline

Archive a team

archive_team
DestructiveIdempotent

Archives a team. Its drive and channel stay. Only when the person clearly asks for it.

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

Input Schema

NameRequiredDescriptionDefault
teamIdYesTeam id from list_teams.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault
archivedYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.8/5.0
Behavior4/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 covered. The description adds the non-obvious behavioral fact that the team's drive and channel are preserved, which tells the agent exactly what is and isn't destroyed, plus a consent precondition. It doesn't mention reversibility (unarchive) or whether membership/roles are affected, keeping it below a 5.

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 very short sentences, each earning its place: what happens, what survives, and the consent condition. The effect and the preserved resources are front-loaded with no filler.

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?

An output schema exists, so return values need no explanation, and the two parameters are fully described in-schema. What the description covers — effect, preservation, consent guardrail — is sufficient for a simple 2-param mutation; only the reversal path (how to restore an archived team) is left unstated.

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%: both teamId ("Team id from list_teams") and workspace ("Workspace slug from workspaces.list") are documented with provenance. The description adds no meaning beyond the schema, so the baseline 3 is correct for a 0-enum, 2-parameter tool.

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?

"Archives a team" is a specific verb+resource, and "Its drive and channel stay" scopes the operation as partial rather than a cascading delete, which separates it from remove_team_drive / remove_team_channel. It stops short of naming the sibling that would be the actual alternative (e.g. a full removal or archive_channel), so sibling routing is only implied.

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?

"Only when the person clearly asks for it" is a real usage condition — a consent guardrail telling the agent not to archive proactively. However there is no statement of when a different tool is preferable (e.g. archive_channel for a single channel, or a removal tool for true deletion), so guidance is implied rather than explicit.

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