Skip to main content
Glama
Pandafile MCP Server

Pandafile MCP Server

Official
by pandafileco

List file requests

list_file_requests
Read-onlyIdempotent

Retrieve your account's file requests with their upload links, open status, and incoming upload counts. Use the returned cursor to page through results.

Instructions

The account's file requests (upload pages) with their links, whether they are open and how many uploads came in. 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_file_requests"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many (1–100, default 20).
cursorNonext_cursor from the previous call.

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 readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description still adds real behavioral value by describing what comes back (links, open/closed state, upload counts) and how paging works via next_cursor, though it says nothing about result volume limits or ordering.

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?

Two sentences, zero filler, with the resource and return shape front-loaded and the pagination instruction reserved for the end where an agent will look for it after the first call.

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 simple two-parameter read with full schema coverage and no output schema, the description is nearly sufficient: it explains the payload fields and paging. It leaves ordering, total counts, and what an empty account returns unstated, which is a minor but real 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 both limit and cursor are already documented, which sets the baseline at 3. The description reinforces the cursor contract ('Pass next_cursor as cursor for the next page') but adds no format, default, or constraint detail beyond 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 gives a specific verb and resource ('The account's file requests (upload pages)') and enumerates the returned fields — links, open status, upload counts — which clearly separates it from siblings like create_file_request or close_file_request. It stops short of naming an alternative explicitly, so a 4 rather than a 5.

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 only implied: the phrasing 'The account's file requests' signals an account-wide listing, and the second sentence covers pagination. There is no explicit statement of when to use this versus get_transfer or other listing tools, and no prerequisites or exclusions are given.

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