Skip to main content
Glama
Sign In
flipper-mcp

flipper-mcp

by yairhdz24
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

flipper_upload_file

Upload a local file to a specified path on the Flipper Zero's SD card and verify its integrity with MD5 checksum.

Instructions

Upload a local file from this computer to a path on the Flipper's SD card; verifies 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": {
      "local_path": "<local_path>",
      "dest_path": "<dest_path>"
    },
    "name": "flipper_upload_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
dest_pathYes
local_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description must disclose behavioral traits. It mentions md5 verification and specifies source/destination, which adds value. However, it does not state whether the operation overwrites existing files, requires a connection, or any error handling details, leaving gaps for a mutation tool.

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 sentence effectively communicates the action, source, destination, and a key behavioral detail (md5 verification). Every phrase is purposeful and front-loaded, with no wasted words.

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 simple tool with two parameters and no output schema, the description covers the core functionality and parameter semantics. It falls short only in not mentioning prerequisites like device connection or behavior on existing files, but overall it is reasonably complete.

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

Parameters4/5

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

The schema provides only parameter names and types with no descriptions. The description clarifies that local_path refers to a file on this computer and dest_path is a path on the Flipper's SD card, giving essential meaning that the schema lacks.

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?

The description clearly states the tool uploads a local file to a path on the Flipper's SD card, with a specific verb and resource. It distinguishes from sibling tools like flipper_write_file by emphasizing the local-to-device transfer and the md5 verification step.

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 description implies usage for transferring a file from this computer to the Flipper, but it does not explicitly mention alternatives or when not to use it. Sibling tools like flipper_write_file suggest a similar yet distinct purpose, but no direct comparison is provided.

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

Deploy Server

Other Tools