Skip to main content
Glama

flipper_storage_write

DestructiveIdempotent

Upload a local PC file to the Flipper Zero SD card and verify it with an MD5 checksum to confirm file integrity.

Instructions

Upload a local PC file to the Flipper SD and verify it by MD5.

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_write"
  }
}

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.4/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 readOnlyHint=false, so the write semantics are covered structurally. The description adds value beyond that by disclosing the post-write MD5 verification step, which is not visible in any structured field. However, it never states what gets destroyed (an overwrite of an existing remote file) even though destructiveHint implies exactly that risk.

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 the source, destination and verification behavior in order, and zero filler words. Nothing could be trimmed without losing meaning.

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?

An output schema exists, so the MD5 verification result need not be described in prose, and the annotations carry the safety profile. What is missing is modest but real: overwrite behavior and remote path format for a two-param destructive write.

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 0% and both properties are bare strings, so the description carries the burden. It does usefully disambiguate direction by tying local_path to "local PC file" and remote_path to "Flipper SD", but it gives no path format, root conventions (e.g. /ext/), or behavior when the local file is missing.

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?

"Upload a local PC file to the Flipper SD and verify it by MD5" names a specific verb (upload), both endpoints of the transfer, and an extra verification step, which clearly separates it from flipper_storage_download. It stops short of naming that sibling or any other alternative, but the action and direction are unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance, no mention of overwriting an existing file at remote_path, and no pointer to alternatives such as flipper_storage_download for the reverse direction. The agent must infer the context entirely from the single sentence.

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