Skip to main content
Glama
Sign In
google-nice-mcp

google-nice-mcp

by Schneckenhausmann
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

drive_read_file

Read the text content of any Drive file using its ID. Supports Docs, Sheets, Slides, PDF, and Office files, with configurable truncation.

Instructions

Read the text content of a Drive file by its id (from drive_search).

Handles Google Docs, Sheets and Slides (exported to text/CSV) as well as PDF, Word (.docx), Excel (.xlsx) and PowerPoint (.pptx) files. Long files are truncated to max_chars; raise it to read more.

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_charsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

Discloses truncation behavior and supported file formats. No annotations exist, so description carries the burden. Lacks details on permissions, failure modes, or read-only nature.

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 concise sentences, front-loaded with purpose. Every sentence provides essential info with no redundancy.

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?

Given output schema exists, description doesn't need return values. Covers file types, truncation, and ID origin. Could mention plain text output or CSV for Sheets, but it's still effective.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 0% description coverage. Description adds meaning: file_id is 'from drive_search', max_chars default is 20000 and adjustable. Both parameters are explained beyond the schema.

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?

Clear verb+resource: 'Read the text content of a Drive file by its id'. Explicitly distinguishes from siblings like drive_search (finds files) and gmail tools.

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?

Tells when to use: 'Handles Google Docs, Sheets and Slides ... PDF, Word, Excel, PowerPoint'. Provides guidance on max_chars for truncation. Could be more explicit about when not to use, but sibling context clarifies.

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