Skip to main content
Glama
Pandafile MCP Server

Pandafile MCP Server

Official
by pandafileco

List transfers

list_transfers
Read-onlyIdempotent

Retrieve an account's transfers newest first with link, size, expiry and download counts. Choose active or history views, search by title, id, recipient or file name, and page with cursors.

Instructions

The account's transfers, newest first, with link, size, expiry and download counts. view "active" (default: live and still uploading) or "history" (expired, deleted, blocked). Pass next_cursor as cursor for the next page.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_transfers"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewNo"active" (default) or "history".
limitNoHow many (1–100, default 20).
queryNoSearch title, id, recipient email or file name.
cursorNonext_cursor from the previous call, for the next page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds real behavioral context beyond that: result ordering (newest first), the payload fields, and the pagination contract of feeding a prior next_cursor back as cursor. Missing only things like default page size behavior, which the schema supplies.

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?

Three short clauses, front-loaded with the resource and ordering before the filter and paging details; every sentence carries information. The phrasing "Pass next_cursor as cursor" is slightly clipped and could be a touch clearer, but nothing is wasted.

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 naming the returned fields and the pagination mechanism, and the zero-required-parameter nature is clear from the schema. Only the search parameter and default limit are undocumented in prose, both of which the schema fully covers.

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 baseline would be 3, but the description genuinely enriches the view enum by explaining what each value actually contains (live/uploading vs expired/deleted/blocked) and clarifies the cursor-to-next_cursor relationship that the schema only hints at. The query and limit parameters are left entirely to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource (list the account's transfers) and adds scope details: newest-first ordering and the fields returned (link, size, expiry, download counts). It does not explicitly contrast with get_transfer or list_file_requests, so an agent must infer that this is the collection-level listing rather than a single-item fetch.

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?

The view semantics ("active" = live and still uploading, "history" = expired, deleted, blocked) implicitly tell the agent which view to pick for which situation, and the cursor instruction covers paging. However, there is no explicit statement about when to use this tool instead of get_transfer or list_file_requests, and no exclusions or prerequisites.

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