Skip to main content
Glama

drive_read

Read-onlyIdempotent

Read Google Drive file metadata and a safe text preview when available using a file ID, so agents can inspect file details before processing.

Instructions

Read Google Drive file metadata and a safe text preview when available.

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

Input Schema

NameRequiredDescriptionDefault
file_idYesGoogle Drive file id
access_tokenNoGoogle Drive access token

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world, so the safety profile is covered. The description adds a genuinely new fact, that the text preview is 'safe' and only available 'when available' (i.e., not for binary/unpreviewable files), but leaves unclear what 'safe' means, whether size limits apply, or how the access_token is used.

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?

A single front-loaded sentence with no filler; every clause (metadata, text preview, availability caveat) carries information.

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?

With no output schema, the description is the only source of return-shape information, and it names only two outputs without saying what metadata fields, preview length, or truncation behavior to expect. It is adequate to select the tool but thin for interpreting results.

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 both parameters (file_id, access_token) are documented in the schema. The description adds no format, scope, or auth detail beyond what the schema already states, so the baseline of 3 applies.

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?

The description gives a specific verb+resource (read a Google Drive file) and adds scope (metadata plus a text preview). It implicitly contrasts with the sibling drive_search (search vs. read-by-id) but never names the alternative 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 statement of when to use this tool versus drive_search, onedrive_read, or dropbox_read_file, and no prerequisites. The only hint at usage is that it takes a specific file, which an agent must infer from 'file metadata'.

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