Skip to main content
Glama

drive read file

drive_read_file
Read-onlyIdempotent

Read text content from Google Drive files for analysis or summarization, exporting Google-native files to text with a size cap.

Instructions

Read a Drive file's text content. Google-native files are exported to text; size-capped.

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": "drive_read_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_idYes
max_bytesNo

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 readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds two real behavioral facts beyond that — Google-native files get exported to text, and output is size-capped — but gives no cap value, no truncation behavior, and no indication of failure on unreadable/binary files.

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?

Two short, front-loaded sentences with no filler — the core operation comes first, the Google-native caveat second. It is efficient, though the terseness is partly where the missing detail should have gone.

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 the tool is simple (one required param). Still, for a read tool with 0% schema coverage and an unexplained truncation parameter, the definition leaves an agent guessing about limits and unsupported file types.

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%, so the description must carry parameter meaning and it largely does not. 'size-capped' gestures at max_bytes but never explains what that parameter does, its default (null), units, or what happens on overflow; file_id's meaning is left entirely to the parameter name.

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: reading a Drive file's *text* content, with the Google-native export case called out. The 'text content' framing implicitly distinguishes it from a binary download, but no sibling (drive_download_file, drive_get_file) is named explicitly.

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?

There is no when-to-use guidance: nothing says to prefer this over drive_download_file or drive_get_file, nor what happens with non-text/binary files. The only actionable hint is that the output is size-capped, which is a limitation rather than a routing rule.

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