fastmcp-gsuite

by tumf

Overview Schema Source Related Servers Discussions Admin

Python

Remote

copy_drive_file

Create a copy of a Google Drive file, with optional new name and target folder.

Instructions

Create a copy of a file in Google Drive.

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": {
      "user_id": "<user_id>",
      "file_id": "<file_id>"
    },
    "name": "copy_drive_file"
  }
}

Input Schema

Name	Required	Description
`user_id`	Yes	The EMAIL of the Google account. Choose from:
`file_id`	Yes	ID of the file to copy.
`new_name`	No	New name for the copied file. If not specified, the original name will be used.
`parent_folder_id`	No	ID of the parent folder for the copy. If not specified, the copy will be in the same folder as the original.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Jun 21, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations provided, so description carries full burden. It only says 'create a copy' but does not disclose behavioral traits like permission preservation, file size limits, or whether comments/revisions are copied.

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?

Very concise, single sentence, no fluff. However, the brevity sacrifices useful information that would help the agent.

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 file copy operation with no output schema, the description is incomplete. It lacks details on return value, error conditions, permission requirements, and how the copy behaves regarding ownership or sharing.

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%, so baseline 3. The description adds no additional meaning beyond the schema descriptions, which already explain each parameter adequately.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states 'Create a copy of a file in Google Drive', which is a specific verb+resource. It distinguishes from sibling tools like delete, move, rename.

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?

No guidance on when to use this tool vs alternatives. With many Drive sibling tools (e.g., move, rename), the description should indicate scenarios for copying vs other operations.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.