Skip to main content
Glama

Coline

Remove a drive from a team

remove_team_drive
DestructiveIdempotent

Unlinks a drive from a team; access to the drive doesn't change.

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>",
      "driveId": "<driveId>"
    },
    "name": "remove_team_drive"
  }
}

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
removedYes

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 and idempotentHint=true, so the safety profile is covered. The description adds genuinely new behavioral context by clarifying the blast radius — the drive itself and its access grants survive the unlink — which is exactly the reassurance an agent needs before calling a destructive-flagged tool. It doesn't say whether the operation is reversible or how to restore the link, 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?

A single compound sentence that front-loads the action and appends the one non-obvious consequence. Every clause earns its place and there is no filler or restatement of the title.

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 tool is a simple three-required-parameter unlink. The description covers the action and its key side effect; only minor omissions remain, such as reversibility and the undocumented driveId.

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 coverage is 67%: teamId and workspace carry inline descriptions pointing at list_teams and workspaces.list, while driveId is undocumented in both schema and description. The description adds no parameter meaning of its own, so the baseline 3 applies — the schema does most of the work and one gap remains unfilled.

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?

Uses a specific verb ("unlinks") plus both resources (drive, team), which is far more precise than the title's "Remove" and implicitly contrasts with the add_team_drive sibling. It stops short of explicitly naming an alternative, but an agent can tell what the operation does without opening the schema.

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?

The verb "unlinks" plus "access to the drive doesn't change" implies the intended scenario: severing a team-drive association rather than deleting or revoking anything. There is no explicit when-to-use/when-not guidance and no mention of the complementary add_team_drive or of permissions needed, leaving the agent to infer usage.

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