Skip to main content
Glama

flipper_info

Read-onlyIdempotent

Retrieves a Flipper Zero's device details, including firmware, hardware, radio, battery, and region, so AI agents can inspect status and configuration.

Instructions

Return the Flipper's device_info (firmware, hardware, radio, battery region).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered structurally. The description adds value by disclosing what categories of data come back (firmware, hardware, radio, battery region), but says nothing about freshness, whether values are cached, or whether the device must be connected.

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?

A single sentence with the action and the returned field categories front-loaded. Every element earns its place; there is no filler or redundant restatement of the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter, read-only, annotated tool with an output schema that documents the return shape, the description needs only to state what the call retrieves, which it does. No prerequisites or payload explanation are missing given the structured fields already present.

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 takes zero parameters, so the schema has nothing for the description to clarify and the baseline is 4. The parenthetical does add meaning by hinting at what the returned payload covers, though it stops short of explaining finer distinctions like battery level versus battery region.

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?

The description names a specific verb ('Return') and resource ('device_info') and enumerates the contents (firmware, hardware, radio, battery region), so an agent knows exactly what it gets. It does not explicitly contrast with the closest sibling, flipper_status, or flipper_storage_info, which keeps it from a 5.

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?

Usage is only implied: it is evidently the tool for reading static device identity details, and the zero-parameter signature removes any ambiguity about invocation. There is no explicit when-to-use or when-not-to-use statement, and no named alternative for overlapping reads such as flipper_status.

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