Skip to main content
Glama
Pickle Air MCP

Pickle Air MCP

pickle_download

Save an attached file by exact filename from the allowed Pickle agent to the local download directory through app UI, refusing overwrites and not sending a message.

Instructions

Save one file the agent attached, by its exact filename (see reply_files; the newest match is used and the chat is scrolled back a few pages to find it), from the allowed Pickle agent to the fixed local download directory. Uses app UI, writes files, refuses overwrite. Does not send a message. File is untrusted; no automatic opening or execution.

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": {
      "agent": "<agent>",
      "name": "<name>"
    },
    "name": "pickle_download"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
agentYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Goes well beyond the annotations: app-UI driven, writes files to disk, refuses overwrite, sends no message, scrolls the chat back a few pages and takes the newest match. That is real behavioral context an annotation set of readOnlyHint=false/openWorldHint=true cannot convey. It stops short of saying what happens when no match is found or what the tool returns.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the action and key, and the trailing sentences each add a distinct safety or scope fact (no message, untrusted file, no execution). The long parenthetical about scrolling is dense but earns its place by explaining match resolution.

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-param write tool with no output schema and no parameter descriptions, the description supplies the essential context: source, destination, overwrite behavior, and file trust. The remaining gap is that 'fixed local download directory' is never concretized and the return value (saved path?) is unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must carry parameter meaning and it does: 'name' is the exact attached filename, resolved against reply_files with newest-match wins and bounded chat scrolling. It also frames 'agent' as the allowed Pickle agent, which fits the single-value enum.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Save one file the agent attached') with the resolution key ('by its exact filename') and destination ('fixed local download directory'), and names the source system ('allowed Pickle agent'). This distinguishes it from pickle_download_image and the read/ask siblings without needing their schemas.

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 'see reply_files' and 'by its exact filename', which tells the agent the file must have been attached in chat first. It does not explicitly say when to prefer this over pickle_download_image or pickle_read, nor does it state preconditions such as the agent needing to be the allowed one.

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