Skip to main content
Glama
Sign In

DataToRAG

by com.datatorag
OverviewDiscussionsAdmin

gws-mcp__drive_copy_file

Copies a file in Google Drive and names the copy in the same call. The copy carries the original's tabs, formatting and formulas, so a copied template matches its source. With convert set to true, an Excel, Word or PowerPoint file is copied as a Google Sheet, Doc or Slides file, which the sheets_, docs_ and slides_ tools open; the original is left as it was. With target_mime_type, the copy is converted to the Google type named, which is how a PDF or an image becomes a Google Doc with its text recognised (ocr_language sets the language for that recognition); when convert and target_mime_type are both given, target_mime_type decides the type. Returns the copy's id, name, MIME type, folders and link. Folders are not copyable: Drive refuses them with a 403 "This file cannot be copied by the user", a limit of the API rather than of permissions.

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_id": "<file_id>",
      "name": "<name>"
    },
    "name": "gws-mcp__drive_copy_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName for the new copy
accountNoOptional email address of the connected account to use (e.g. 'user@gmail.com'). If omitted, the default account is used.
convertNoWhen true, the copy of an Excel, Word or PowerPoint file is a Google Sheet, Doc or Slides file (.xlsx and .xls to Sheets, .docx and .doc to Docs, .pptx and .ppt to Slides). A file of any other type is refused and nothing is copied. Defaults to false, a copy of the same type. Ignored when target_mime_type is given.
file_idYesThe Google Drive file ID to copy
parent_idNoFolder ID to place the copy in (optional, defaults to the original's folder)
ocr_languageNoLanguage hint for the text recognition when a PDF or image is converted to a Google Doc, as a BCP-47 code such as en, de or ja. Optional; Drive detects the language when it is absent.
target_mime_typeNoThe Google type the copy is converted to, e.g. application/vnd.google-apps.document for a Google Doc (a PDF or image copied this way has its text recognised), application/vnd.google-apps.spreadsheet or application/vnd.google-apps.presentation. Sent to Drive as the copy's mimeType, with no lookup of the source's type; Drive refuses a conversion it does not support. Optional; takes precedence over convert.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only mark it as a non-read, non-destructive write. The description adds substantial behaviour the annotations cannot convey: the original is left as it was, tabs/formatting/formulas are preserved, unsupported types are refused with nothing copied, and folders fail with a 403 that is an API limit rather than a permissions problem. It also states the return payload (id, name, MIME type, folders, link).

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?

It is front-loaded with the core action, then layers conversion semantics and the folder limit, so an agent can stop reading early. It is on the long side and some of the convert/target_mime_type detail duplicates the schema descriptions verbatim, which slightly exceeds what the description needs to carry.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 7-parameter mutation tool with no output schema, the description covers what is copied, what is preserved, how conversion and OCR behave, the precedence rule, the failure mode for folders, and the return fields. Nothing an agent needs in order to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents each parameter. The description still adds real meaning — the precedence of target_mime_type over convert, the fact that target_mime_type is sent directly with no source-type lookup, and why ocr_language matters only for PDF/image conversions. That is value beyond the schema, though it is largely restated rather than extended for file_id, name and parent_id.

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?

The first sentence states a specific verb and resource ('Copies a file in Google Drive') plus the added convenience of naming the copy in one call. It is clearly distinguishable from siblings like drive_move_file, drive_rename_file, drive_upload_file and sheets_copy_tab_to, since it copies whole files rather than moving, renaming, creating or copying a tab.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

The description gives explicit selection rules for the two conversion paths: use convert for Office-to-Google conversions, use target_mime_type for PDF/image-to-Doc OCR, and it resolves the conflict by stating target_mime_type takes precedence. It also rules out a category with 'Folders are not copyable'. It stops short of naming a sibling alternative (e.g. drive_upload_file for brand-new content), so a 4 rather than 5.

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

All DataToRAG toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources