Skip to main content
Glama
Sign In
FlipperTalk

FlipperTalk

by ReconGrunt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

flipper_type_text

Types ASCII text directly into a Flipper Zero device, character by character, for faster input than navigating an on-screen keyboard.

Instructions

Type a string directly into the device, one character at a time. Far better than arrow-keying an on-screen keyboard for filling in text fields. Requires Momentum or RogueMaster firmware.

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": {
      "text": "<text>"
    },
    "name": "flipper_type_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
portNoSerial port (e.g. COM7, /dev/ttyACM0). Omit when one Flipper is attached.
textYesASCII text to type
delayNoSeconds between characters

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.4/5.0
Behavior4/5

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

Description adds that typing is one character at a time with a configurable delay. Annotations already show non-destructive mutation. No contradictions. Could mention need for focus on a text field, but adequate.

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?

Two sentences, front-loaded with purpose and key benefit. No wasted words. Extremely efficient.

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 3-parameter tool with no output schema, description covers purpose, benefit, and firmware requirement. Could briefly mention that the device must be in a text input mode, but not strictly necessary.

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?

Schema coverage is 100%, so baseline 3. Description adds that text is ASCII and typed character-by-character, adding meaning beyond schema. Port and delay parameters are already clear in schema.

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?

Clearly states it types a string into the device one character at a time, with specific benefit over arrow-keying. Distinguishes from sibling tools like flipper_input and flipper_input_sequence by focusing on text entry.

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

Usage Guidelines4/5

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

Explicitly recommends use for filling text fields and mentions firmware requirement. Implies it's better than alternatives but doesn't list specific when-not-to-use scenarios or explicitly name alternatives.

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