Skip to main content
Glama

Dropbox

by io.github.pipeworx-io
OverviewAdmin

Dropbox Download

dropbox_download
Read-onlyIdempotent

Download a file from Dropbox and return its content as text plus metadata (size, type, modified date). Use to retrieve file contents for processing or inspection.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesFile path to download

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoError code if connection failed
contentNoDownloaded file content as text
messageNoError message if connection failed
metadataNoFile metadata from download response

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "content": {
+      "description": "Downloaded file content as text",
+      "type": "string"
+    },
+    "error": {
+      "description": "Error code if connection failed",
+      "type": "string"
+    },
+    "message": {
+      "description": "Error message if connection failed",
+      "type": "string"
+    },
+    "metadata": {
+      "description": "File metadata from download response",
+      "properties": {
+        "id": {
+          "description": "Unique file ID",
+          "type": "string"
+        },
+        "modified": {
+          "description": "Last modified timestamp",
+          "type": "string"
+        },
+        "name": {
+          "description": "File name",
+          "type": "string"
+        },
+        "path_display": {
+          "description": "Display path",
+          "type": "string"
+        },
+        "size": {
+          "description": "File size in bytes",
+          "type": "number"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "path": "/Documents/contract.pdf"
+  }
+]
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, non-destructive, and idempotent behavior. The description adds the return format (content as text plus metadata), which is useful for setting expectations. It does not contradict annotations and supplements them with functional output details.

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?

The description is two short sentences that state purpose and use case directly, with no unnecessary words or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simple one-parameter interface, the presence of an output schema, and the clear description of what the tool returns, the description provides sufficient context for an agent to select and invoke the tool correctly.

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?

The input schema fully documents the only parameter, 'path', as 'File path to download'. The description does not add further syntax or format details; thus the schema carries the semantic load, so baseline 3 is appropriate.

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 clearly identifies the action ('Download') and resource ('file from Dropbox'), and distinguishes itself from sibling tools by specifying the return of content plus metadata (size, type, modified date). This makes the tool's purpose unambiguous.

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 explicitly states when to use the tool: 'Use to retrieve file contents for processing or inspection.' While it does not enumerate alternative tools, the context implies a clear use case that differs from metadata-only tools like dropbox_get_metadata or listing via dropbox_list_folder.

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

All Dropbox toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources