Skip to main content
Glama

Coline

Create a shared drive

create_shared_drive

Makes a new shared drive in the team workspace. Only the workspace's owner can.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
accessModeNorestricted

Output Schema

NameRequiredDescriptionDefault
driveYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent, closed-world write. The description adds the owner-only authorization rule, which is genuinely useful context not in the annotations. It omits duplicate-name behavior and what the non-idempotent guarantee means in practice.

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?

Two short sentences, front-loaded with the action and followed by the permission constraint. Minor weakness: the second sentence is a fragment and 'Makes' is informal for a creation verb, but nothing is wasted.

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

Completeness3/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. For a 3-parameter creation tool with an undocumented accessMode default and no uniqueness rules, though, the description leaves an agent guessing about side effects of the creation.

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 33%: only the workspace parameter is documented in the schema. The description mentions neither name constraints nor the accessMode enum with its 'restricted' default, 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?

Provides a clear verb and resource: creating a shared drive in the team workspace. It does not differentiate itself from look-alike siblings such as add_team_drive or create_team, so it stops short of a 5.

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 sentence 'Only the workspace's owner can' gives a real precondition for use, which is more than nothing. However, there is no guidance on when to choose this over add_team_drive or how it relates to other creation tools, so usage is only implied.

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