Skip to main content
Glama

drive_read

Read-onlyIdempotent

Read a file from the registered Google Drive folders: a Google Doc or Slides file as text, a Sheet as rows of values (the first sheet, or range such as 'Sheet1'!A1:D20), or a plain-text file. Up to 2 MB of text. PDF and Office files are not read here: use drive.import to bring them into the workspace's files. file is a Drive id or a pasted 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": {
      "file": "<file>"
    },
    "name": "drive_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYesDrive id or pasted link.
rangeNoSheets only: A1 range, e.g. 'Sheet1'!A1:D20. Default: the first sheet.
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds behavior the annotations cannot: a 2 MB text cap and the format-normalization semantics (Docs/Slides become text, Sheets become rows of values), which materially affect how an agent should call and consume the result.

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?

Front-loads the core action and supported file types, then the limit, then the exclusion/alternative. Dense but nearly every clause carries information; the enumeration of formats is slightly long but justified by the branching read behavior.

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

Completeness4/5

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

For a read tool with no output schema, the description adequately conveys what comes back (text or rows of values) and the size ceiling. It could say more about result structure or behavior when a file is missing/unshared, but nothing essential for correct invocation is missing.

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 `file`, `range`, and `in_workspace` are already documented. The description restates the `file` type (Drive id or pasted link) and the range behavior, adding little beyond the schema, and it never mentions `in_workspace` at all. 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?

Opens with a specific verb and resource ("Read a file") and immediately enumerates the supported cases: Docs/Slides as text, Sheets as rows of values, plain-text files. It also names the sibling it is not (drive.import) for PDF and Office files, so an agent can distinguish it without opening the 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?

Explicitly states the exclusion condition ("PDF and Office files are not read here") and names the alternative tool to use instead, which is strong routing guidance. It does not cover how to obtain a Drive id in the first place (e.g., drive_search/drive_list) or when to prefer range-based reads, leaving a small gap.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.