Skip to main content
Glama
Pandafile MCP Server

Pandafile MCP Server

Official
by pandafileco

Close a file request

close_file_request
Idempotent

Stop a file request from accepting new uploads; existing files remain, and the request can be reopened from the dashboard.

Instructions

Stop a file request from accepting uploads (its upload page then says it is closed). Files already uploaded stay. It can be reopened from the dashboard.

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": "close_file_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesFile request id (from create_file_request or list_file_requests).

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?

Beyond the annotations (destructiveHint=false, idempotentHint=true), the description discloses that already-uploaded files are preserved and that the requester-facing page reflects a closed state. Reversibility via the dashboard is also stated, which is meaningful behavior for a state-changing tool. It does not cover permission requirements or whether in-flight uploads are interrupted.

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?

Three short sentences, each carrying distinct information: the effect, the side-effect on existing files, and the reversibility path. The state change is front-loaded with zero filler.

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 one-parameter state-change tool with annotations already covering the safety profile and no output schema, the definition covers effect, preservation of data, and reversibility. Only auth/permission expectations are absent, which is a minor gap at this complexity.

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?

There is a single parameter with 100% schema description coverage, and the schema already explains the id and its origin (create_file_request or list_file_requests). The description adds no further meaning about the identifier, so the baseline of 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 concrete verb and resource — 'Stop a file request from accepting uploads' — and clarifies the resulting state ('its upload page then says it is closed'). It is naturally distinguishable from create_file_request and list_file_requests, though no sibling is named 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?

Usage is implied by the effect (use when you want to stop accepting uploads), and the note that it 'can be reopened from the dashboard' suggests this is a reversible interim step. It does not explicitly say when to prefer this over alternatives such as deleting or leaving the request open, so guidance remains inferred.

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