Skip to main content
Glama
Pandafile MCP Server

Pandafile MCP Server

Official
by pandafileco

Add recipients

add_recipients
Idempotent

Email a transfer's download link to additional recipients. Each new address receives a personal link, while addresses already on the transfer are skipped.

Instructions

Email the transfer's link to more people: each new address gets an email with a personal download link. Addresses already on the transfer are skipped.

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>",
      "emails": "<emails>"
    },
    "name": "add_recipients"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTransfer id: the last part of the share link (https://pandafile.co/d/<id>), e.g. "k3x9q2m7ab".
emailsYesEmail addresses to add (1–50).

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=false, idempotent=true, openWorld=true and destructive=false. The description adds real behavior beyond them: an outbound email is sent to each new address, each contains a personal download link, and existing addresses are silently skipped rather than erroring. Not covered: whether the call is rejected for invalid/expired transfers, or what is returned about which addresses were skipped.

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 short sentences: the effect first, then the dedupe rule. Every clause carries information an agent needs, with no filler or repetition of the title.

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 two-parameter mutation with annotations covering the safety profile, the description gives the essential side effect (emails sent with personal links) and the idempotent skip behavior. With no output schema, it stops short of saying what the caller learns about skipped or newly added addresses, which is the only meaningful 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 coverage is 100%, with the id parameter documented by example and emails bounded at 1–50, so the baseline is 3. The description's statement that addresses already on the transfer are skipped adds genuine meaning about how the emails array is interpreted beyond the schema. It says nothing further about the id parameter, but the schema already carries that.

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 names a concrete action and object: it emails a transfer's download link to additional people, i.e. adds recipients to an existing transfer. 'More people' and 'already on the transfer are skipped' make clear this augments an existing share rather than creating one, which separates it from create_file_request/send_files. The verb is 'email' rather than 'add', so an agent must infer that recipient records are persisted, but the intent is still unambiguous.

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: use this when you want to distribute an existing transfer's link to new addresses. There is no explicit contrast with remind_recipient (re-notify existing recipients) or get_transfer (inspect current recipients), so an agent must infer the boundary between adding and reminding. No prerequisites (ownership, transfer expiry) are stated.

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