Skip to main content
Glama
Sign In
Egnyte Large File Manager

Egnyte Large File Manager

by hschickdevs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Egnyte: download file to disk

egnyte_download
Read-only

Download an Egnyte file's real binary to local disk. Returns the local file path for code access, supporting large files via streaming.

Instructions

Download an Egnyte file's REAL binary to local disk and return the local path (not the bytes). Use this when you need to load a file with code — e.g. pandas/openpyxl on .xlsx, parse a native PDF, read a .msg. Streams, so large files are fine. Provide the Egnyte path (e.g. /Shared/Docs/report.xlsx).

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": {
      "egnyte_path": "<egnyte_path>"
    },
    "name": "egnyte_download"
  }
}

Input Schema

NameRequiredDescriptionDefault
egnyte_pathYesEgnyte path, e.g. /Shared/Docs/report.xlsx
entry_idNoSpecific version entry_id (optional)
destNoLocal destination file path or directory (optional; defaults to the download dir)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Describes streaming for large files and return of local path. Annotations already declare readOnlyHint and openWorldHint; description adds value by specifying behavior beyond annotations (streaming, large file handling). No contradictions.

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?

Three sentences, front-loaded with core purpose. Second sentence provides when-to-use context. Third sentence gives path example. No wasted words; concise and informative.

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?

Covers key aspects: what it downloads, how it returns, parameter usage. With no output schema, it explains return value. Minor gaps: no mention of overwrite behavior or error handling, but sufficient for typical use.

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 coverage 100% with descriptions. Description adds context: explains path format with example, clarifies return value. Adds value beyond schema by tying parameters to usage scenario.

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 'download' and resource 'Egnyte file's REAL binary to local disk'. Distinguishes from siblings by specifying it returns a local path, not bytes, and mentions use cases (pandas, openpyxl). Differentiated from egnyte_stat and egnyte_upload.

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?

Explicitly says when to use: 'when you need to load a file with code' with examples. Implicitly excludes metadata operations (sibling egnyte_stat) and uploads (egnyte_upload). Lacks explicit 'do not use for' statements, but guidance is clear.

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