Skip to main content
Glama
nabheet

google-services-mcp

by nabheet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Download Drive file

google_drive_download

Download raw bytes from non-Google-native Google Drive files, returning decoded text or base64, or save them to a local path.

Instructions

Download a file's raw bytes (non-Google-native files). Text content returns decoded text; binary returns base64. Pass saveToPath to write bytes to a local file instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fileIdYesDrive file ID.
accountNoAccount nickname to use.
saveToPathNoLocal path to write the raw bytes to (returns { savedTo } instead of data).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.60
    • addedInput schema / properties / saveToPath
      Added value: +{
+  "description": "Local path to write the raw bytes to (returns { savedTo } instead of data).",
+  "type": "string"
+}
  2. Addedv0.1.30

TDQS

A4.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose the key behavioral trait of return format (decoded text vs base64) and the response-shape switch when saveToPath is used, but says nothing about authentication/account requirements, file-size or rate limits, or whether saveToPath overwrites an existing local file.

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 short sentences, each earning its place: scope constraint first, then return-format behavior, then the saveToPath alternative. Front-loaded and free of filler.

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 compensates by describing the return payload (decoded text vs base64, { savedTo } when saving), which is exactly what an agent needs to interpret the result. Remaining gaps (auth, size limits) are secondary for a read-only byte-fetch tool.

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 description coverage is 100%, so all three parameters are already documented, including saveToPath's 'returns { savedTo } instead of data'. The description reinforces saveToPath's effect but adds no syntax or format detail beyond the schema; baseline 3 applies.

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?

States a specific verb (Download) and resource (a file's raw bytes), and adds a scope qualifier (non-Google-native files) that implicitly routes Google-native files to the sibling google_drive_export. An agent can distinguish this from google_drive_get and google_drive_export without opening a schema.

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 parenthetical '(non-Google-native files)' acts as an exclusion that tells the agent when this tool applies versus export, and 'Pass saveToPath to write bytes to a local file instead' gives concrete usage guidance for the optional parameter. It stops short of explicitly naming google_drive_export as the alternative.

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

Deploy Server

Other Tools