Skip to main content
Glama
Pandafile MCP Server

Pandafile MCP Server

Official
by pandafileco

Get a transfer

get_transfer
Read-onlyIdempotent

Retrieve detailed information about a file transfer by its ID, including share link, status, expiry, files, recipients, downloads, approvals, comments, and link statistics.

Instructions

One transfer in detail: link, status, expiry (and the latest expiry possible), files, recipients (who was emailed, who downloaded), latest downloads, approvals/comments from recipients and link statistics (views, downloads, countries).

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": "get_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/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile needs no restating. The description's real contribution is disclosing the shape and depth of the response payload — recipient-level email/download detail, approvals, and geographic statistics — which is valuable given there is no output schema. It does not say what happens when the id is unknown or whether access requires ownership, keeping it below a 5.

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?

A single sentence front-loads the core statement ("One transfer in detail") before the field list, and every clause names a distinct part of the response. There is no filler or repetition of the title or annotations.

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 and one fully documented parameter, the description appropriately spends its budget describing the returned data, which is the main gap it needed to close. It stops short of covering failure behavior for an unknown or unauthorized id, which is the only notable omission for a simple idempotent read.

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 single `id` parameter is documented in the schema with format and an example ("k3x9q2m7ab"). The description adds nothing about the identifier, so the baseline 3 applies with the schema doing all 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?

"One transfer in detail" states a specific verb and resource and contrasts implicitly with list-style siblings by emphasizing a single record. It then enumerates exactly what the result contains (link, status, expiry, files, recipients, downloads, approvals, statistics), so an agent can tell precisely what this returns without opening another schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: the singular framing plus the required `id` in the schema makes clear this fetches one known transfer, but there is no explicit when-to-use, no when-not, and no named alternative (e.g., list_transfers for discovery). An agent must infer the routing decision from the phrasing alone.

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