flipper-mcp

by yairhdz24

Overview Schema Source Related Servers Discussions Admin

Python

flipper_read_file

Retrieve file contents from a Flipper Zero device, with text decoded automatically or base64 when binary is requested.

Instructions

Read a file from the Flipper. Text is returned decoded; set binary=true to get base64.

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": {
      "path": "<path>"
    },
    "name": "flipper_read_file"
  }
}

Input Schema

Name	Required	Description	Default
`path`	Yes
`binary`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 2, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations provided, the description adds valuable behavioral context by explaining that text is decoded by default and binary=true returns base64. It does not disclose error behavior or explicitly confirm read-only safety, but the core behavior is clearly conveyed.

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 entire description is a single, front-loaded sentence that avoids redundancy. Every word earns its place, efficiently conveying the tool's purpose and the key binary option.

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 2-parameter tool with an output schema, the description provides sufficient context for basic usage. It does not mention potential errors or path conventions, but the low complexity and presence of an output schema reduce the need for extra detail.

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?

Schema description coverage is 0%, but the description compensates by explaining the binary parameter's effect (base64 output) and implicitly clarifies path as the file location. It does not elaborate on path format or constraints, but the essential semantics are covered.

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 (Read) and the resource (a file from the Flipper), with an additional behavior detail about decoded text vs. base64 binary. It distinguishes itself from sibling tools like flipper_list_dir and flipper_stat by focusing on file content retrieval.

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 reading file contents, but does not explicitly mention when to use it versus alternatives (e.g., flipper_stat for metadata) or state any exclusions. The binary flag guidance is parameter-focused rather than providing contextual when-to-use advice.

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