Skip to main content
Glama

drive_rename

Change the name of a file or folder in the registered Google Drive folders. file is a Drive id or a pasted link.

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": {
      "file": "<file>",
      "name": "<name>"
    },
    "name": "drive_rename"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYesDrive id or pasted link.
nameYesThe new name.
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=false), so the description carries a lighter burden and it does add that only registered folders are reachable. However, it does not disclose what happens on an invalid id, whether the previous name is recoverable, or whether renaming a folder affects path-based references — all real behavior for a mutation. Adequate but not rich.

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?

Two sentences, zero filler, and the actionable scope constraint is front-loaded before the parameter hint. Nothing is repeated unnecessarily and the size matches the tool's simplicity.

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?

For a three-parameter rename with full schema coverage, complete annotations, and no output schema, the definition gives an agent enough to call it correctly. The residual gap is behavioral rather than structural — no note on permissions or side effects — but that is a modest omission given how much the annotations already cover.

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 100%: `name` carries a maxLength of 255 and `in_workspace` is documented in detail in the schema itself. The description only restates that `file` accepts an id or pasted link, which the schema already says verbatim, so it adds essentially no meaning beyond the structured data. Baseline 3 applies.

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 definition opens with a concrete verb+resource pair ('Change the name of a file or folder') and bounds the scope to 'the registered Google Drive folders', which tells an agent exactly what object class it can touch. It stops short of naming any sibling or contrast case (e.g. content edits via drive_replace / drive_update_range), so differentiation is implied by the resource rather than stated.

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 statement, no mention of prerequisites such as write permission on the target folder, and no routing to alternatives. The only guidance is the negative scope 'registered Google Drive folders', which an agent must interpret on its own.

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.