Skip to main content
Glama

Coline

Set drive access

set_drive_access
DestructiveIdempotent

Sets whether everyone in the workspace can open a drive, or only the teammates and roles given.

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

Input Schema

NameRequiredDescriptionDefault
grantsNo
driveIdYesDrive id from list_drives.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
accessModeYes

Output Schema

NameRequiredDescriptionDefault
driveYes
grantsYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the agent knows this is a mutation. The description adds nothing about what is destroyed: since grants is optional and defaults to an empty array, an agent cannot tell whether omitting grants wipes existing grants or leaves them untouched, nor what the response contains.

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 front-loaded sentence that opens with the verb and resource and then explains the access modes. Nothing is wasted, though the phrasing is slightly dense and could front-load which mode is the default.

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?

For a destructive mutation with an output schema (so return values need no explanation), the description is too thin: it omits permission prerequisites, whether grants replaces or merges with existing access, and what happens when grants is omitted, all of which an agent needs before calling it.

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 50%, and the description does map its two modes onto accessMode (workspace_default vs restricted) and gestures at grants ('teammates and roles given'). However the grant object's fields (subjectType, subjectId, action with read/write/manage) and the 200-item cap are left entirely undocumented in prose.

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?

States a specific verb (sets) and resource (drive access) and explains the two outcomes: everyone in the workspace vs. named teammates and roles. It is clear what the tool does, though it never names the read-side counterpart get_drive_access to draw the boundary explicitly.

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 when-to-use guidance at all: no mention of required admin privileges, no statement that get_drive_access should be used to inspect current access first, and no guidance on choosing between workspace_default and restricted beyond a restatement of what each means.

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