Skip to main content
Glama

Coline

Add a drive to a team

add_team_drive

Links a drive the person can open to a team.

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

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
teamDriveYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

C2.9/5.0
Behavior3/5

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

The annotations already declare the write, non-destructive, non-idempotent, closed-world profile, so the description's burden is reduced. It usefully adds the prerequisite that the drive must be openable by the person, but it says nothing about the effect of isDefault, how duplicates or pre-existing links are handled, or required permissions.

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 short sentence with no filler, with the core action front-loaded. Its brevity is efficient, though it borders on under-specification rather than tightness.

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

Completeness2/5

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

This is a four-parameter mutation verb with an output schema, yet the description explains neither isDefault semantics, duplicate-link behavior, nor permission requirements. Output schema coverage excuses return-value detail, but the input-side behavior remains incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%: teamId and workspace are documented in the schema, but driveId and isDefault are undocumented in both schema and description. The description adds no parameter meaning at all, so it fails to compensate for the coverage gap.

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 states a specific verb and resource: it 'links a drive... to a team', which is concretely distinguishable from siblings like add_team_member or create_shared_drive. The qualifier 'the person can open' adds a scope condition but doesn't name any sibling it competes with.

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 explicit when-to-use or when-not-to-use guidance, and no mention of remove_team_drive as the inverse operation. The only implied condition is the precondition that the drive must already be accessible to the person, which is a usefulness hint rather than usage guidance.

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