Skip to main content
Glama

flipper_storage_download

DestructiveIdempotent

Downloads a file from a Flipper Zero to your PC, preserving binary data and supporting files up to 64 MB.

Instructions

Download a file from the Flipper to the PC (binary-safe, up to 64 MB).

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": {
      "remote_path": "<remote_path>",
      "local_path": "<local_path>"
    },
    "name": "flipper_storage_download"
  }
}

Input Schema

NameRequiredDescriptionDefault
local_pathYes
remote_pathYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=false, so the safety profile is covered. The description adds two genuinely useful traits beyond that: binary-safe transfer and a 64 MB size cap. It does not disclose what the destructive hint means in practice — notably whether an existing local file at local_path is overwritten.

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?

A single front-loaded sentence with no filler; the verb and direction come first and the parenthetical constraints follow. Every clause adds information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A return-value explanation is unnecessary because an output schema exists, and annotations cover safety. However, for a destructive two-parameter file transfer with zero schema documentation, missing overwrite behavior, path format, and source-missing handling leaves real gaps.

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

Parameters2/5

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

Schema description coverage is 0%, so both parameters are undocumented in structured fields, and the description never mentions them by name. The only implied meaning is that remote_path lives on the Flipper and local_path on the PC, with no path syntax, directory creation behavior, or overwrite semantics.

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?

States a specific verb (download) and resource (a file from the Flipper to the PC), and the directional phrasing implicitly separates it from flipper_storage_read and flipper_storage_write. It stops short of naming a sibling, so an agent must infer the distinction from direction alone.

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 only implied through the 'from the Flipper to the PC' direction and the 64 MB cap, which suggests when this is preferable to an in-device read or write. There is no explicit when-to-use, when-not, or named alternative.

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