Skip to main content
Glama

Coline

Rename a drive

rename_drive
Idempotent

Renames a shared drive the person manages.

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

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
driveYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the useful permission constraint that the caller must manage the drive, but says nothing about failure modes (name collision, duplicate names, non-manager errors) beyond that.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence with zero waste, but it is arguably under-specified rather than concise; there is no structure beyond the bare claim and nothing front-loaded about authorization behavior or outcomes.

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 not be explained, and the tool is a simple three-parameter mutation with annotations carrying the safety profile. Still, for a mutation gated on management rights, the description leaves error and constraint behavior 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 coverage is 67% — driveId and workspace are already documented in the schema, and 'name' is self-evident given the minLength/maxLength constraints. The description adds no format, syntax, or uniqueness semantics for the new name, so it does not compensate for the remaining 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?

States a specific verb and resource ('Renames a shared drive') and adds the scoping qualifier 'the person manages'. It does not differentiate itself from near-neighbors such as rename_group_chat or update_drive_file, 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only usage signal is the implicit authorization condition 'the person manages'; there is no statement of when to use this versus other drive-mutation tools, no prerequisites, and no exclusions. An agent must infer everything about selection.

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