Skip to main content
Glama

read_drive_file

Read-onlyIdempotent

Reads a workspace document by path and resolves MIME type ambiguity so an agent can retrieve the correct file contents.

Instructions

Read a document from the workspace store by path with MIME disambiguation.

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": {
      "path": "<path>"
    },
    "name": "read_drive_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.1

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds only the store scope and the hint that result handling depends on MIME type; it says nothing about missing-file behavior, binary vs. text return, or size limits.

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?

A single front-loaded sentence with no filler — the verb, resource, key, and scope arrive immediately. The one weak spot is that the closing clause consumes words while remaining ambiguous rather than earning its place.

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?

For a one-parameter read tool with no output schema and complete safety annotations, most of the burden is lifted. Still missing is any statement of what a read returns (text, base64, parsed document) or what happens on a bad path, which an agent needs before calling.

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 0%, so the description must carry parameter meaning. It does add that the single argument is a path into the workspace store, but gives no format, root convention, or extension-handling detail, leaving 'MIME disambiguation' unexplained relative to the path argument.

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 names a specific verb and resource ('Read a document from the workspace store') plus the lookup key ('by path'), which lets an agent separate it from write_drive_file and the git blob/tree readers. The trailing phrase 'with MIME disambiguation' is genuinely vague — with only a path parameter it is unclear whether MIME is inferred from the extension or resolved by the server.

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: 'by path' tells the agent this is the tool for when a path is already known, which implicitly distinguishes it from search_drive_rag. However, it never names an alternative or states when not to use it, and the several sibling readers (krusch_fs_read_page, krusch_git_read_blob) are left unaddressed.

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