Skip to main content
Glama
Sign In
flipper-mcp

flipper-mcp

by yairhdz24
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

flipper_stat

Identify whether a path is a file or directory and get its size on the Flipper Zero. Retrieve filesystem details over USB to manage device storage.

Instructions

Get type and size of a file or directory on the Flipper.

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

Input Schema

NameRequiredDescriptionDefault
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that the tool returns type and size, and the verb 'Get' implies a read-only operation. However, it does not mention error behavior, path format requirements, or any side effects, which is a gap for a tool with no annotations.

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 concise sentence that conveys the tool's purpose without unnecessary words. It is front-loaded with the verb and resource, and every word adds value.

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

Completeness3/5

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

The tool is simple (one parameter, no output schema), and the description covers the core purpose. However, given the lack of annotations and output schema, the description could have been more complete by mentioning how the size is reported (e.g., bytes) or what happens for nonexistent paths. It is adequate but has clear gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and there is only one parameter 'path'. The description implies the path refers to a file or directory on the Flipper, but it does not specify whether the path must be absolute, relative, or how to format it. This is only minimal compensation for the lack of schema-level documentation.

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 specifies exactly what the tool does: it gets the type and size of a file or directory on the Flipper. This distinguishes it from sibling tools like flipper_list_dir (which lists contents) and flipper_read_file (which reads content), making it clear this is for metadata.

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 description implies usage (when you need to know the type or size of a path on the Flipper) but does not explicitly state when to prefer this tool over alternatives. It does not mention exclusions or alternative tools, so it provides only implicit guidance.

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

Deploy Server

Other Tools