Skip to main content
Glama
Pandafile MCP Server

Pandafile MCP Server

Official
by pandafileco

Send files with Pandafile

send_files

Upload local files or folders to Pandafile and get a shareable download link; optionally email recipients personal links. Preserves folder structure and supports chunked uploads for large files.

Instructions

Upload local files and/or folders to Pandafile and get a share link (https://pandafile.co/d/). Folders are sent with their structure. Large files are fine (resumable, chunked uploads); the call returns when the upload is complete. If recipients are given, each gets an email with a personal download link. Returns the link, id, expiry and sizes. Only send files the user asked you to send.

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": {
      "paths": "<paths>"
    },
    "name": "send_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathsYesAbsolute paths of files or folders on this computer (~ is expanded), e.g. ["/Users/ada/Desktop/final-cut.mov", "/Users/ada/Desktop/stills"].
titleNoTitle shown on the download page and in emails (up to 120 characters).
messageNoMessage to the recipients (up to 1000 characters).
passwordNoDownload password (8–200 characters). Recipients need it to download. Plus/Pro/Team only.
expires_atNoExact expiry as ISO 8601 (e.g. "2026-12-31T23:00:00Z"). Alternative to expires_in_days; same limits.
recipientsNoEmail addresses to send the link to. Leave out to just get a link.
expires_in_daysNoKeep the files this many days from now (1–90). Pro/Team only, at most 90 days after sending; not for test keys. Leave out for the plan default.

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?

Annotations already flag the write/open-world/non-idempotent profile, and the description adds real value on top: resumable chunked uploads, that the call blocks until upload completes, that folders keep their structure, and that recipients each get a personal email link. It omits failure/retry behavior and plan/quota constraints, so it is not exhaustive.

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?

Six short clauses, front-loaded with what the tool does and the link format, then progressively less critical details, ending with the consent guardrail. No filler sentences.

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 no output schema, the description compensates by enumerating the return values (link, id, expiry, sizes). For a 7-parameter write tool, remaining gaps are minor: no mention of size/quota limits, password behavior, or what happens on interruption.

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 is 100%, so the baseline is 3; the description earns an extra point by explaining the effects of parameters rather than restating them — recipients trigger per-person emails with personal links, and folder paths preserve structure. It says nothing about password or expiry semantics beyond what the schema already documents.

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?

States a specific verb and resource ('Upload local files and/or folders to Pandafile and get a share link'), including the resulting link format. The 'local files' framing implicitly separates it from the URL-import sibling without needing to name it.

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?

'Only send files the user asked you to send' gives a clear consent guardrail, and the local-path scope implies when this is preferred over a URL-based send. It never explicitly says when not to use it or names an alternative tool, so it stops short of a 5.

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