flipper-mcp

by yairhdz24

Overview Schema Source Related Servers Discussions Admin

Python

flipper_rename

Renames or moves a file/directory on a Flipper Zero over USB with just the old and new paths.

Instructions

Rename or move a file/directory on the Flipper.

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": {
      "old_path": "<old_path>",
      "new_path": "<new_path>"
    },
    "name": "flipper_rename"
  }
}

Input Schema

Name	Required	Description	Default
`new_path`	Yes
`old_path`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 2, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations are provided, so the description bears full responsibility for disclosing behavior. It does not mention whether overwriting occurs, path constraints, failure modes, or side effects, leaving critical behaviors undisclosed.

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?

The description is a single, direct sentence with no filler or redundancy. It is perfectly concise for its low complexity.

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

Completeness2/5

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

Despite having an output schema, the description omits important contextual details such as error conditions, overwrite behavior, and whether the operation is atomic. The tool supports both files and directories but gives no further guidance, making it incomplete for a rename/move operation.

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 coverage is 0% with only titles 'Old Path' and 'New Path'. The description adds the concept of renaming/moving a file/directory, which implies old-to-new mapping, but it does not clarify path formats, constraints, or relationships between the two parameters beyond their names.

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 action ('Rename or move') and the resource ('a file/directory on the Flipper'), distinguishing it from sibling file operations like read, write, delete, or list.

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 guidance on when to use this tool versus alternatives, no prerequisites mentioned, and no exclusions or conditions. The intended use is implied but not explicitly stated.

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