Skip to main content
Glama
Google Workspace MCP connector

Google Workspace MCP connector

by animesh-ex

docs_read

Read-only

Read a Google Doc as readable Markdown or structured paragraphs and tables with start/end indices for precise edits.

Instructions

Read a Google Doc. format 'markdown' returns readable text; 'structured' returns each paragraph/table with its start/end index (needed for precise edits).

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": {
      "documentId": "<documentId>"
    },
    "name": "docs_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNomarkdown
documentIdYes

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 declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds valuable behavioral detail by explaining the two return shapes: markdown gives readable text, while structured gives paragraph/table indices for precise edits.

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?

Two sentences, front-loaded with the core action, followed by a compact explanation of the format choice. There is no wasted wording.

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 simple two-parameter read tool with no output schema, the description covers the key return-value distinction between markdown and structured output and explains why structured matters for edits. The only minor gap is that documentId is not explicitly described.

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 0%, so the description must carry parameter meaning. It does a good job explaining what the 'format' enum values produce, but it does not describe the required 'documentId' parameter, relying on the self-explanatory name.

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?

The description states a specific verb and resource: 'Read a Google Doc.' This clearly distinguishes a read operation from sibling mutation tools such as docs_batch_update, docs_insert_markdown, and docs_delete_range, and the Google Doc resource differentiates it from sheets_read and slides_read.

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?

The description explains the two format modes but gives no explicit guidance on when to use this tool versus alternatives such as drive_read_file_text or docs_batch_update. The note that 'structured' is 'needed for precise edits' is parameter-level guidance rather than tool-selection guidance.

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