Skip to main content
Glama
Sign In
FlipperTalk

FlipperTalk

by ReconGrunt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

flipper_alert

Activate the audiovisual alert on your Flipper device to locate it by sound and light flash.

Instructions

Play the audiovisual alert -- the 'find my Flipper' beep and flash.

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

Input Schema

NameRequiredDescriptionDefault
portNoSerial port (e.g. COM7, /dev/ttyACM0). Omit when one Flipper is attached.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/5.0
Behavior2/5

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

Annotations indicate non-destructive and non-read-only behavior. The description merely restates that it plays an alert, providing minimal extra context beyond the annotations. No disclosure of side effects or failure modes.

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?

Single, succinct sentence that communicates the purpose immediately. No filler or redundancy.

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?

For a tool with no output schema and a single optional parameter, the description covers the essential action and parameter usage. However, it lacks details about the alert's behavior (e.g., duration, repetition).

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 schema describes the 'port' parameter. The description adds meaningful usage context: 'Omit when one Flipper is attached', which aids the agent in deciding whether to include it.

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 clearly states the verb 'Play' and the resource 'audiovisual alert', specific to the 'find my Flipper' feature. It effectively distinguishes this tool from siblings by naming the unique alert behavior.

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 the user wants to trigger a physical alert on the Flipper device, but it does not explicitly state when to use or when to avoid it, nor does it reference alternatives among siblings.

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