Skip to main content
Glama
Pandafile MCP Server

Pandafile MCP Server

Official
by pandafileco

Delete a transfer

delete_transfer
DestructiveIdempotent

Permanently remove a transfer and its files so the share link stops working for everyone. This action cannot be undone, so confirm with the user before deleting.

Instructions

Delete a transfer now: its files are removed for good and the link stops working for everyone. This cannot be undone – confirm with the user first.

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": {
      "id": "<id>"
    },
    "name": "delete_transfer"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTransfer id: the last part of the share link (https://pandafile.co/d/<id>), e.g. "k3x9q2m7ab".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the destructiveHint and idempotentHint annotations, the description discloses exactly what is destroyed (the files), who is affected (everyone with the link), and that the effect is irreversible. It also states the operational guardrail to confirm with the user before calling, which annotations cannot convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences with the action and consequence front-loaded and the safety instruction last where it is most salient. Every clause carries information, though the tool's simplicity leaves the overall size close to minimal rather than rich.

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 single-parameter destructive tool with full annotation coverage and no output schema, the description covers consequences, irreversibility, and the confirmation gate. Only a passing note on what happens to recipients or whether the call returns a confirmation is absent, which is minor.

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%, and the sole 'id' parameter is already documented with format, length bounds, and an example. The description adds no additional meaning about how to obtain or format the id, which is an acceptable baseline when the schema does the work.

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 names a specific verb and resource ('Delete a transfer') and immediately states the blast radius: files are removed permanently and the share link stops working for everyone. That distinguishes it clearly from non-destructive siblings like get_transfer or update_transfer.

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 supplies usable context for when to invoke it (when the transfer and its files should be gone for good) and a mandatory precondition ('confirm with the user first'). It stops short of naming an alternative for the adjacent case, such as revoking access without destroying files, so it lacks explicit exclusions.

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