Skip to main content
Glama

Coline

Read a file

read_file
Read-onlyIdempotent

Reads a Drive file's text (extracted from PDFs, Office files and Coline's own formats), a window at a time: pass nextOffset as offset to keep reading, or a query for the most relevant excerpt.

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

Input Schema

NameRequiredDescriptionDefault
queryNo
fileIdYesFile id from list_drive_files, search or fetch.
offsetNo
maxCharsNo
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault
fileYes
noteYes
contentYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful behavior about windowed reading and excerpt retrieval, but omits limits such as maxChars truncation behavior and what nextOffset looks like in the response.

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?

One dense sentence front-loads the core purpose and then the pagination mechanism, with no filler. The nested clauses make it slightly harder to scan than a two-sentence split would, but nothing is wasted.

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?

With an output schema present, return values need not be explained, and annotations cover safety. The definition covers the two main modes (continuation and query) adequately, though it leaves maxChars and the precise nextOffset contract implicit.

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 only 40%, and the description meaningfully clarifies offset ('pass nextOffset as offset') and query ('most relevant excerpt'). However, maxChars is never explained, and the mismatch between the description's 'nextOffset' and the schema's 'offset' parameter name adds ambiguity rather than resolving it.

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 and resource ('Reads a Drive file's text'), names the extraction sources (PDFs, Office files, Coline formats), and explains the windowed-read model. It doesn't explicitly distinguish itself from sibling readers like read_sheet or read_board_activity, so it falls short of a 5.

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?

It tells the agent how to continue reading ('pass nextOffset as offset') and that a query returns the most relevant excerpt, which implies the two usage modes. It does not state when to prefer query mode over offset pagination, nor when this tool is the wrong choice compared with sibling readers.

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.

Resources