Skip to main content
Glama

flipper_find

Read-onlyIdempotent

Recursively search the Flipper Zero SD card for files or folders by case-insensitive name match. Returns full paths and uses a call budget to stay responsive on large trees.

Instructions

Recursively search the SD for files/folders whose name contains name (case-insensitive), starting at path. Call-budgeted so it stays fast on big trees. Returns matching full paths. Great for 'where is X' before a task.

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": {
      "name": "<name>"
    },
    "name": "flipper_find"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
pathNo/ext
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 closed-world, so the safety bar is covered. The description adds real behavior beyond that: recursion over the whole tree, case-insensitive substring matching, and a call budget that keeps it fast on large trees. It omits what happens when the budget is exhausted (silent truncation vs. error), which matters for trusting completeness of results.

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?

Three tight sentences, front-loaded with the core semantics, then the performance trait, then the use case. No filler and nothing repeated from the schema.

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 return values need little explanation, and the description still notes it returns matching full paths. For a search tool with a budget parameter, the missing note on truncation behavior is the only substantive 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%, so the description carries the burden. It explains `name` well (substring, case-insensitive) and implies `path` as the search root, but `max_calls` is only obliquely referenced via 'call-budgeted' — its effect on result completeness is never described.

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 ('Recursively search the SD for files/folders') plus the matching rule (name contains `name`, case-insensitive) and the starting point (`path`). This clearly separates it from a flat listing tool like flipper_storage_list, though it never names a sibling explicitly.

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 an explicit usage context: 'Great for "where is X" before a task,' which tells the agent when to reach for this instead of a directory listing. It stops short of stating when NOT to use it (e.g., when you already know the directory and just want to enumerate it).

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