Skip to main content
Glama
Sign In
FlipperTalk

FlipperTalk

by ReconGrunt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

flipper_write_file

Write files to a Flipper Zero device. Automatically creates parent directories as needed.

Instructions

Write a file to the device, creating parent directories as needed.

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>",
      "content": "<content>"
    },
    "name": "flipper_write_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
portNoSerial port (e.g. COM7, /dev/ttyACM0). Omit when one Flipper is attached.
contentYes
encodingNoutf-8

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?

Description adds behavioral detail beyond annotations (which are neither read-only nor destructive) by stating that parent directories are created. However, it does not disclose overwrite behavior, error handling, or file size limits.

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?

Single sentence efficiently conveys the core action and key auxiliary behavior. No redundant phrases.

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?

For a write operation with no output schema, the description lacks details on return values, error conditions, and the state of the device before/after, making it insufficient for safe autonomous use.

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?

With only 25% schema description coverage, the description adds no further meaning to the parameters. It does not explain what content format is expected or the required path syntax, leaving the schema to carry the burden.

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?

Description uses specific verb 'write' and resource 'file', and adds unique behavior 'creating parent directories as needed', clearly distinguishing it from siblings like flipper_read_file and flipper_mkdir.

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?

No guidance on when to use this tool vs alternatives, such as flipper_upload or flipper_delete. The description does not mention prerequisites or context.

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