Skip to main content
Glama

drive download file

drive_download_file
Read-onlyIdempotent

Download a Google Drive file to the server's designated download directory. The destination is path-traversal guarded to keep saved files inside the allowed sandbox.

Instructions

Download a Drive file into the server's download directory (path-traversal guarded).

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>",
      "destination": "<destination>"
    },
    "name": "drive_download_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_idYes
destinationYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=true, so safety is largely covered. The description usefully adds that a file is materialized on the server's disk at a fixed download directory and that path traversal is guarded — behavior not in the annotations. However, it leaves open what happens on name collisions/overwrites and how the required "destination" parameter relates to the fixed download directory, which is a real ambiguity given the readOnly hint.

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?

A single front-loaded sentence with no filler; the parenthetical guard is well placed. It is efficient, though the size comes at the cost of the missing parameter guidance rather than from deliberate tightness.

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

Completeness3/5

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

An output schema exists, so return values need not be described, and annotations cover the safety profile. Still, with two required, completely undocumented parameters and an unclear relationship between "destination" and the fixed download directory, the definition leaves the agent guessing on inputs for a file-writing side effect.

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

Parameters2/5

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

Schema description coverage is 0% — neither file_id nor destination has any explanation. The description does not compensate: it never says what file_id accepts (ID vs. path vs. URL) or what "destination" means, and in fact its "server's download directory" phrasing conflicts conceptually with a required destination argument.

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?

States a specific verb and resource ("Download a Drive file") plus the outcome location ("server's download directory"), so an agent knows exactly what happens. It does not distinguish itself from nearby tools like drive_read_file or drive_get_file, which is the only clarity gap.

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 when-to-use guidance and no named alternative. An agent cannot tell from the description whether to download vs. read a file, or what preconditions (permissions, file type, size) apply.

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