Skip to main content
Glama
Pandafile MCP Server

Pandafile MCP Server

Official
by pandafileco

Remind a recipient

remind_recipient

Resend a transfer recipient's personal link and reactivate their reminders, limited to twice per hour per recipient. Use it when a recipient needs their access link again.

Instructions

Email a recipient of the transfer their personal link again (and turn their reminders back on). At most twice an hour per recipient.

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>",
      "email": "<email>"
    },
    "name": "remind_recipient"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTransfer id: the last part of the share link (https://pandafile.co/d/<id>), e.g. "k3x9q2m7ab".
emailYesA recipient of this transfer.

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 declare a non-read-only, non-destructive, non-idempotent, open-world operation, and the description adds genuinely new context: an outbound email is sent, the recipient's reminders are re-enabled as a side effect, and a 2/hour/recipient rate limit applies. These are details not derivable from the name or annotations. It stops short of describing failure behavior for an email that is not a recipient.

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 compact sentences with the core action first and the constraint second; no redundant restatement of the title or schema. Every clause carries information.

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 tool with no output schema and full annotation coverage, the description supplies the action, an important side effect, and a rate limit. Remaining gaps are minor: what happens when the email is not an existing recipient and whether a response body is returned.

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%, with 'id' documented down to the share-link format and 'email' constrained to a recipient of the transfer. The description adds no syntax or semantic detail beyond the schema, 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 uses a specific verb and resource ('Email a recipient of the transfer their personal link again'), making clear this is a resend/reminder action rather than a new invite. The parenthetical about turning reminders back on adds precision. It does not explicitly name a sibling like add_recipients, so conflict avoidance is inferred from 'again' rather than stated.

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 rate limit ('At most twice an hour per recipient') gives an operational boundary for when the call is valid, which is useful. However, there is no explicit when-to-use vs when-not-to-use guidance, no statement of preconditions (e.g., the recipient must already exist on the transfer), and no named alternative if the goal is to add someone new.

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