Skip to main content
Glama

flipper_storage_delete

DestructiveIdempotent

Deletes a file or empty directory from the Flipper Zero SD card by path, enabling AI agents to manage device storage.

Instructions

Delete a file or (empty) directory on the Flipper SD.

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

Input Schema

NameRequiredDescriptionDefault
pathYes

Output Schema

NameRequiredDescriptionDefault
resultYes

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?

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered by structured data. The description adds the meaningful behavioral constraint that only empty directories can be removed. It does not mention irreversibility, failure modes, or what happens if the path does not exist, so it adds some but not rich context.

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 short sentence with no filler, front-loading the action and the target. Every word, including the '(empty)' qualifier, carries information.

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

Completeness3/5

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

An output schema exists, so return values need not be explained, and the annotations cover destructiveness. Still, for a destructive one-parameter tool with zero schema coverage on that parameter, the description should specify path format and the behavior on non-empty or missing paths.

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?

The single 'path' parameter has 0% schema description coverage, so the description carries the full burden. It only implies that the path refers to a file or directory on the SD card; it gives no format guidance (absolute vs relative, leading slash, root notation), which leaves an agent guessing about a destructive call.

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?

The description uses a specific verb ('Delete') and resource ('a file or (empty) directory on the Flipper SD'), which clearly separates it from siblings like flipper_storage_write, flipper_storage_mkdir and flipper_storage_read. The '(empty)' qualifier adds real precision. It does not name a sibling alternative, so it stops short of a 5.

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 parenthetical '(empty)' implies a precondition — directories must be emptied before deletion — which is implicit usage guidance. However, there is no explicit statement of when to prefer this over siblings, no note about what to do with non-empty directories, and no prerequisite or confirmation guidance for a destructive operation.

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