flipper-mcp

Overview Schema Source Related Servers Discussions Admin

flipper_list_apps

Lists applications available to the Flipper Zero loader, revealing installed FAPs and built-in settings apps to clarify what can be launched.

Instructions

List apps available to the loader (installed FAPs and built-in settings apps).

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 2, 2026

TDQS

A4.4/5.0

Behavior4/5

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

No annotations are provided, so the description carries the transparency burden. It clarifies that the tool lists 'installed FAPs and built-in settings apps' and implicitly indicates a read-only operation. While it doesn't explicitly say 'does not modify anything', the verb 'list' and the non-destructive resource context are sufficient for this simple read operation.

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?

The description is a single sentence, 13 words, front-loaded with the verb 'List' and immediately specifies the resource and scope. Every word adds value, and it avoids unnecessary detail or repetition.

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?

The tool is simple with no parameters and has an output schema. The description is sufficient to understand what will be listed and what qualifies. It could have added a note about requiring a connection, but that is likely implied by the tool family and sibling context.

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?

The tool has zero parameters, so the baseline for this dimension is 4. The description adds no parameter details, but no parameters exist, so the schema covers everything. The description's clarification of what counts as an app complements the empty schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb 'List' and identifies the resource as 'apps available to the loader', further clarifying with 'installed FAPs and built-in settings apps'. This clearly distinguishes it from siblings like flipper_list_dir (files) and flipper_app_start (running apps).

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?

The description provides clear context on what the tool lists and the scope ('available to the loader'), which effectively implies when to use it (e.g., to enumerate FAPs vs. files or directories). It does not explicitly mention alternatives or exclusions, but the specificity makes the intended use evident.

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