Skip to main content
Glama
Sign In

DataToRAG

by com.datatorag
OverviewDiscussionsAdmin

gws-mcp__gmail_save_attachment_to_drive

Save a Gmail attachment directly to Google Drive. Use gmail_read first to get attachment metadata (filename, mimeType, attachmentId) from the message parts. The file is fetched from Gmail and uploaded to Drive server-side — no base64 data flows through the conversation. Returns the Drive file metadata including a web 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": {
      "message_id": "<message_id>",
      "attachment_id": "<attachment_id>",
      "filename": "<filename>"
    },
    "name": "gws-mcp__gmail_save_attachment_to_drive"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountNoOptional email address of the connected account to use (e.g. 'user@gmail.com'). If omitted, the default account is used.
filenameYesFilename to save as in Drive (e.g., 'report.xlsx')
message_idYesThe Gmail message ID that contains the attachment
attachment_idYesThe attachment ID from the message part's body.attachmentId field
parent_folder_idNoOptional Drive folder ID to save into. If omitted, saves to the root of My Drive.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false and destructiveHint=false, so the safety profile is already structured. The description adds genuinely new behavioral context: the transfer happens server-side and 'no base64 data flows through the conversation', which materially affects how an agent should plan the call, and it discloses the return shape (Drive metadata plus a web link).

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?

Three sentences, zero filler: purpose first, prerequisite second, transfer mechanics and return value last. Every sentence carries actionable information and nothing is repeated.

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?

With no output schema, the description correctly fills the gap by stating what comes back (Drive file metadata including a web link). Combined with the prerequisite workflow and the server-side transfer note, an agent has everything needed to invoke it correctly.

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%, and the schema already explains account, parent_folder_id defaults, and that attachment_id comes from body.attachmentId. The description largely restates the gmail_read provenance for those parameters rather than adding new meaning, so it sits at the baseline for a fully documented schema.

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 description opens with a specific verb+resource pair ('Save a Gmail attachment directly to Google Drive') that is distinct from sibling tools like gmail_get_attachment (which only retrieves) and drive_upload_file (which pushes local data). An agent can immediately tell this is a cross-service transfer operation.

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?

It gives an explicit workflow prerequisite: 'Use gmail_read first to get attachment metadata (filename, mimeType, attachmentId)'. This is strong when-to-use guidance. It stops short of naming alternatives it competes with (e.g., gmail_get_attachment plus drive_upload_file as a two-step fallback), so it is not a full 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