Skip to main content
Glama

flipper_index

Read-onlyIdempotent

Surveys Flipper Zero firmware, hardware, region, running app, SD free space, and /ext folder tree with per-folder counts to provide read-only structural context before tasks.

Instructions

Survey the device before a task, WITH SUBSTRUCTURE. Returns firmware/hardware/region, running app and SD free space, then a tree of /ext down to depth levels with per-folder file/subdir counts. Folders with many subdirs are counted but not expanded; a call budget (max_calls) keeps it fast. One call = full structural context. Pass a higher depth for more. Read-only.

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

Input Schema

NameRequiredDescriptionDefault
depthNo
max_callsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description reinforces 'Read-only' while adding genuinely new behavior: folders with many subdirs are counted but not expanded, and a max_calls budget bounds runtime. It stops short of stating the actual call-budget failure mode or what happens when the budget is exhausted mid-tree.

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?

Front-loaded with the action and the returns, and the trailing 'Read-only' is well placed. A couple of lines are redundant ('One call = full structural context' largely restates the preceding sentence) and the all-caps 'WITH SUBSTRUCTURE' is stylistic noise rather than information.

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?

An output schema exists, so the description needn't document return shapes, yet it still previews them, which is helpful for a composite survey tool. Nothing critical is missing for correct invocation, though the interaction between depth and max_calls (which one wins when the tree is huge) is left unstated.

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 coverage is 0%, so the description must carry both parameters, and it does: depth is defined as the number of /ext levels expanded ('Pass a higher depth for more') and max_calls is framed as a call budget that 'keeps it fast'. It adds meaning beyond the bare integer types, though it gives no ranges or caveats about very large depth values.

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?

Uses a specific verb-plus-resource framing ('Survey the device') and enumerates exactly what comes back: firmware/hardware/region, running app, SD free space, and a /ext tree with per-folder counts. The phrase 'WITH SUBSTRUCTURE' implicitly separates it from flipper_info / flipper_storage_list, but no sibling is named, so the differentiation is inferred rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Gives a clear trigger: 'Survey the device before a task', and tells the caller how to escalate ('Pass a higher depth for more'). It never states when NOT to use it or which sibling tool to prefer for a flat listing or a deep single-directory browse.

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