Skip to main content
Glama

dropbox_read_file

Read-onlyIdempotent

Read UTF-8 text from a Dropbox file up to 10 MB, returning chunked content at character boundaries for continued processing; PDF and Office files are not supported.

Instructions

Read UTF-8 text from a Dropbox file up to 10 MB, returning chunks at character boundaries. PDF and Office documents are not supported.

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": "dropbox_read_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesFull Dropbox file path
max_bytesNoMaximum bytes to return (default 4000 to fit chat responses, min 4, max 1000000)
start_byteNoZero-based byte offset (default 0). Use the previous result's end_byte to continue.
access_tokenNoDropbox access token

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive behavior. The description adds useful context beyond that: a 10 MB file cap, UTF-8-only support, chunking at character boundaries, and unsupported PDF/Office documents.

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 compact sentences with no waste. The core action is front-loaded, followed immediately by the size, encoding, chunking, and unsupported-format constraints.

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?

The definition is nearly complete for a read-only file tool: annotations cover safety, the schema covers parameters, and the description covers format limits and unsupported types. It does not explain auth requirements, but access_token is documented in the schema.

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 100%, so path, max_bytes, start_byte, and access_token are already fully documented. The description's mention of chunking and character boundaries adds some meaning for continuation, but it does not materially extend the parameter documentation.

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: reading UTF-8 text from a Dropbox file. It also scopes the operation with a 10 MB limit, chunked reads, and unsupported document types, making it clearly distinct from listing or searching siblings.

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?

It gives clear negative guidance that PDF and Office documents are not supported, which helps prevent misuse. However, it does not explicitly route the agent to dropbox_search or dropbox_list_folder when the path is unknown or when a non-text file must be handled.

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