Skip to main content
Glama

flipper_subghz_tx

Transmit a saved Sub-GHz .sub file at a chosen frequency to replay your own garage or gate remote capture on compatible devices. Use only on legal bands and devices you own.

Instructions

Transmit a saved Sub-GHz .sub file at the given frequency (Hz). Transmit only on bands legal where you are, to devices you own (e.g. replay your own garage/gate remote capture).

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

Input Schema

NameRequiredDescriptionDefault
pathYes
frequencyNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnly=false, openWorldHint=true, idempotent=false and destructive=false, so the description's main addition is the legal/ownership caveat, which is genuinely useful context. It does not describe transmission duration, hardware requirements, or failure behavior on an unreadable path or out-of-band frequency.

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 the operation and followed by the constraint. No filler or restatement of the name.

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?

An output schema exists, so return values need not be explained, and the description covers the core action plus the most important safety caveat. Minor gaps remain around prerequisites (device connection, valid .sub format) for a hardware-transmitting mutation tool.

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 description coverage is 0%, so the description carries the burden and does add meaning: 'path' points to a saved .sub file and 'frequency' is expressed in Hz. It does not clarify whether frequency must match the capture's recorded frequency or what happens when omitted.

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?

States a specific verb ('Transmit') and resource ('a saved Sub-GHz .sub file at the given frequency'), so the agent knows exactly what the tool does. The mention of replaying a remote capture further pins down the operation.

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?

Gives clear intended-use context ('replay your own garage/gate remote capture') and a regulatory constraint on which bands to use. It stops short of naming alternatives or stating prerequisites such as a connected Flipper or an existing .sub file path.

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