Skip to main content
Glama

flipper_storage_list

Read-onlyIdempotent

List files and folders on a Flipper Zero SD card by path to inspect storage contents, including directories like /ext, /ext/subghz, and /ext/nfc.

Instructions

List a directory on the Flipper SD (e.g. /ext, /ext/subghz, /ext/nfc).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "flipper_storage_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo/ext

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is fully covered elsewhere. The description contributes only the scope hint that paths live on the SD card via concrete examples; it says nothing about recursion depth, hidden files, behavior for a nonexistent path, or output shape.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One sentence, front-loaded with the action and resource, with examples appended rather than buried. Nothing is wasted, though a brief note on defaults or scope could be added without bloat.

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 annotations cover the safety profile. For a simple one-parameter listing tool this is roughly adequate, but the absence of any usage routing against the many sibling tools leaves a real gap.

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

Parameters3/5

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

Schema description coverage is 0% for the single `path` parameter, so the description carries some burden. The example paths (/ext, /ext/subghz, /ext/nfc) usefully illustrate format and the fact that the tool is SD-card scoped, but the default value /ext and any notion of relative vs absolute paths or trailing slashes are not addressed.

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 names a specific verb (list) and resource (a directory on the Flipper SD), and the parenthetical example paths (/ext, /ext/subghz, /ext/nfc) pin down the domain. It does not, however, distinguish itself from plausible siblings such as flipper_find or flipper_storage_info, 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance and no mention of alternatives (e.g. flipper_find for searching, flipper_storage_info for metadata). The reader must infer from the name and the example paths alone when this tool is the right choice.

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