Skip to main content
Glama

flipper_storage_read

Read-onlyIdempotent

Read a file from Flipper Zero storage, returning printable text as UTF-8 or binary data as base64 and limiting output with max_bytes to keep responses manageable.

Instructions

Read a file from the Flipper. Returns UTF-8 text if printable, else base64 (prefixed 'base64:'). Caps at max_bytes.

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

Input Schema

NameRequiredDescriptionDefault
pathYes
max_bytesNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description does add value beyond them by disclosing the encoding rule (UTF-8 if printable, otherwise 'base64:' prefix) and the max_bytes cap. It omits what happens on a missing/invalid path and whether truncation is signaled when the cap is hit, which matters for a capped read.

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?

Two short sentences, front-loaded with the action and then the return contract; no filler. The 'Caps at max_bytes' fragment is terse to the point of being slightly clipped, but it earns its place.

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 needn't be explained, and safety is covered by annotations. Still, for a file-read tool whose only required parameter is undocumented, the definition should say something about valid path form and behavior when the file is absent or the cap triggers truncation.

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 description coverage is 0%, so the description must carry parameter meaning and largely does not. It clarifies max_bytes as a cap on returned content, but says nothing about 'path' — expected format, absolute vs relative, leading slash, or which storage root — which is the required parameter and the main source of call errors.

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?

States a specific verb and resource ('Read a file from the Flipper') and adds the return-encoding behavior, which distinguishes it from what an agent would guess for the storage siblings. It does not name the closest alternative (flipper_storage_download) to make the read-vs-download split explicit, so it stops short of full differentiation.

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 at all: nothing says whether to prefer this over flipper_storage_download or flipper_storage_info, and no prerequisites about the Flipper being connected or unlocked. Usage is only implied by the return-format note.

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