Skip to main content
Glama
Pandafile MCP Server

Pandafile MCP Server

Official
by pandafileco

Create a file request

create_file_request

Creates a shareable upload link that anyone can use to send files to your account, so you can collect photos or documents from clients.

Instructions

Create a file request: an upload page (link) anyone can use to send files to this account – e.g. to collect photos or documents from a client. Uploads show up as transfers. Needs a live key on Pro/Team.

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": {
      "title": "<title>"
    },
    "name": "create_file_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesWhat you are asking for, shown on the upload page (up to 120 characters).
messageNoInstructions shown on the upload page (up to 1000 characters).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the annotations (which only say this is a non-readonly, non-destructive, non-idempotent, non-open-world write), the description discloses the real effects: the call produces a public upload link, resulting uploads appear as transfers, and an active key on a Pro/Team plan is required. It does not discuss limits on number of requests or what happens to the link after closing, which would round it out.

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 short clauses in a single tight paragraph: definition first, use case second, effect and prerequisite last. No filler or redundant restatement of the name.

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?

For a two-parameter creation tool with no output schema, the description covers what is created, what it yields (a link, with submissions becoming transfers), and the plan/key prerequisite. It leaves the returned object's fields (e.g., an ID needed later for close_file_request) unspecified, which is the only notable gap.

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 description coverage is 100%, so title (max 120, shown on the page) and message (max 1000, instructions shown on the page) are already documented. The description adds only the framing that the page is public-facing, which is helpful context but not parameter-level detail beyond the schema; baseline 3 applies.

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 ('Create a file request') and then defines the artifact concretely as 'an upload page (link) anyone can use to send files to this account', which lets an agent distinguish it from siblings like list_file_requests, close_file_request, or send_files without opening a schema.

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?

Gives a clear use case ('to collect photos or documents from a client') and states the prerequisite 'Needs a live key on Pro/Team'. It stops short of naming an explicit alternative or a when-not condition, so it is clear context rather than full routing guidance.

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