Skip to main content
Glama

flipper_vibro

Idempotent

Toggle the Flipper Zero vibration motor on or off to provide tactile feedback or silence alerts during automated device tasks.

Instructions

Turn the vibration motor on or off.

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": {
      "on": "<on>"
    },
    "name": "flipper_vibro"
  }
}

Input Schema

NameRequiredDescriptionDefault
onYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare the mutation profile (readOnlyHint=false, idempotentHint=true, destructiveHint=false), so the description adds essentially nothing behavioral. It does not say whether the motor stays running after the call returns, whether a duration is implied, or whether the device must be unlocked first — the key unknowns for a physical toggle.

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 front-loaded sentence with no padding or redundancy. Nothing could be removed without losing information.

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 trivial (one boolean, output schema present so return values need no explanation) and the description covers its core action. The only meaningful omissions are persistence of the on-state and any unlock requirement.

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%, but there is only one parameter, a boolean named 'on', and the phrase 'on or off' maps directly onto it, making true/false meaning inferable. It adds no further detail such as default state or effect of repeated calls.

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-plus-resource: it controls the vibration motor and toggles it between two states. It is clearly distinct from hardware siblings like flipper_led and flipper_press, though it doesn't name them explicitly.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, and no mention of alternatives or preconditions. For a single-purpose toggle this is tolerable, but the description leaves the agent to infer all context.

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