Skip to main content
Glama

flipper_loader_open

Launch a Flipper Zero app by name and optionally pass an argument, such as a saved file path, to open the app with that file.

Instructions

Launch an app by name, optionally with an argument (e.g. a file path). Example: flipper_loader_open('Sub-GHz'), or open an app with a saved file.

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

Input Schema

NameRequiredDescriptionDefault
appYes
argsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false and openWorldHint=false, so the mutation/launch profile is covered structurally. The description adds only that an argument can be passed (e.g. a file path); it says nothing about what happens if the app is already running, what an invalid app name does, or whether launch is foreground/blocking.

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 core action and immediately followed by a concrete invocation example. The example slightly restates the first sentence but earns its place by showing the argument form.

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 no explanation, and the tool has only two parameters with one required. The remaining gap is discoverability of valid app names and differentiation from flipper_launch_fap, which keeps it short of complete.

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 must carry parameter meaning, and it does partially: 'app' is an app name and 'args' is an optional argument such as a file path. It still omits format details an agent needs, such as case sensitivity, how app names are discovered (likely via flipper_index), and how multi-token args should be quoted.

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: 'Launch an app by name, optionally with an argument.' Clear what it does, but it never distinguishes itself from the sibling flipper_launch_fap, which plausibly also launches applications, leaving an agent to guess which to pick.

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

Usage Guidelines3/5

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

The example ('flipper_loader_open("Sub-GHz")', or opening an app with a saved file) implies the intended usage context, but there is no explicit when-to-use/when-not guidance and no routing to alternatives such as flipper_launch_fap or flipper_loader_close.

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