Skip to main content
Glama
Pandafile MCP Server

Pandafile MCP Server

Official
by pandafileco

URL import status

get_import_status
Read-onlyIdempotent

Check the progress of a transfer created from URLs, showing bytes received per file and whether each link is ready or failed with its error.

Instructions

Progress of a transfer created with send_from_urls: per file bytes received, then "ready" (the link works) or "failed" (with the error; the transfer is then deleted).

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_import_status"
  }
}

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

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, so the bar is lower. The description still adds real value beyond them: it discloses the per-file byte progress shape, that "ready" means the link works, and notably that a "failed" outcome means the transfer is deleted — an important side effect for a nominally read-only call.

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?

One front-loaded sentence covering purpose, progress output, and both terminal states with a parenthetical clarifying the failure consequence. No filler, nothing redundant.

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 carries the burden of explaining return values and does so at a state level (bytes received → ready/failed with error). Minor gaps remain: no polling cadence and no naming of intermediate/non-terminal states beyond "bytes received".

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. The description adds nothing about the id, so the baseline 3 applies.

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 resource and scope: progress of a transfer created with send_from_urls, and enumerates the terminal states ("ready" vs "failed"). Tying it to the creating sibling send_from_urls distinguishes it from get_transfer, though it never uses a verb like "get"/"poll" explicitly.

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?

"a transfer created with send_from_urls" implies the condition under which this tool applies, which is useful routing. However there is no explicit when-not guidance, no mention of get_transfer for other transfer types, and no indication of how often to poll.

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