Skip to main content
Glama
Google Workspace MCP connector

Google Workspace MCP connector

by animesh-ex

drive_read_file_text

Read-only

Reads a Google Drive file as text: Google Docs as Markdown, Sheets as CSV of the first tab, Slides as text, or plain text, CSV, and JSON files. Set maxChars to limit output length.

Instructions

Read a file's content as text: Google Docs (markdown), Sheets (CSV of first tab), Slides (text), or plain text/CSV/JSON files.

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": {
      "fileId": "<fileId>"
    },
    "name": "drive_read_file_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileIdYes
maxCharsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, openWorldHint), so the description's job is to add behavior, and it does: it discloses that Sheets reads only the first tab and that Docs are converted to markdown, which are real limitations an agent must know. It does not mention truncation, size limits, or failure modes for unsupported formats, keeping it short of a 5.

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 sentence, front-loaded with the verb and resource, followed by a compact per-type breakdown. Every clause carries information; nothing is redundant.

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?

There is no output schema, and the description does a reasonable job describing return formats per file type, which is the main unknown for a read tool. However, for a tool with a maxChars parameter it never explains truncation behavior, and it is silent on what happens with unsupported or binary files.

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% for two parameters, so the description carries the full burden and provides none: 'fileId' is never mentioned and 'maxChars' — which has a default of 100000 and an enormous numeric range — is never explained as a truncation control. Only the implicit notion of 'a file' hints at fileId.

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 and resource ('Read a file's content as text') and then enumerates exactly what the text output is for each Drive file type: markdown for Docs, CSV of the first tab for Sheets, text for Slides, and raw text/CSV/JSON otherwise. This per-type output spec functionally separates it from binary-download and metadata siblings without needing to name them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: an agent can infer it should call this when it needs readable content instead of metadata (drive_get_file) or raw bytes (drive_download_file). There is no explicit when-to-use/when-not-to-use sentence and no guidance on what to do for unsupported file types.

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