Skip to main content
Glama
Sign In
FlipperTalk

FlipperTalk

by ReconGrunt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

flipper_gpio_otg

Toggles the 5V OTG power rail on the GPIO header to supply or cut power to attached peripherals.

Instructions

Turn the 5V OTG rail on the GPIO header 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": {
      "enabled": "<enabled>"
    },
    "name": "flipper_gpio_otg"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior2/5

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

Annotations already indicate the tool is not read-only. The description adds minimal behavioral context beyond the basic toggle action; it does not disclose potential side effects (e.g., power draw, impact on other GPIO operations) or prerequisites.

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, complete sentence with no filler words. It is efficiently front-loaded and conveys the essential 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?

For a simple on/off toggle, the description is fairly complete given the schema's coverage. It lacks mention of return values or interactions with other tools, but overall suffices.

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 coverage is 50% (port has description, enabled does not). The description does not add any parameter-specific details beyond the schema, meeting the baseline for this coverage level.

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 action ('Turn the 5V OTG rail... on or off') with a specific verb and resource, distinguishing it from sibling tools like flipper_gpio_read or flipper_gpio_write that deal with general GPIO pins.

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?

No explicit guidance on when to use this tool versus alternatives is provided. The context is implied—if you need to control the OTG power rail—but no conditions or exclusions are mentioned.

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