flipper-mcp

Overview Schema Source Related Servers Discussions Admin

flipper_ir_send

Transmit infrared signals to control devices by specifying protocol, address, and command. Supports NEC, Samsung32, RC5, and more.

Instructions

Transmit an infrared signal. protocol e.g. NEC, NECext, Samsung32, RC5, RC6, SIRC. address and command are hex (e.g. 0x04, 0x08).

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": {
      "protocol": "<protocol>",
      "address": "<address>",
      "command": "<command>"
    },
    "name": "flipper_ir_send"
  }
}

Input Schema

Name	Required	Description	Default
`address`	Yes
`command`	Yes
`protocol`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 2, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of disclosing behavior. It only says 'Transmit an infrared signal,' which implies an action but does not explain side effects, whether the Flipper must be connected, potential blocking behavior, or any other operational details. This is a significant gap.

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 two sentences, front-loaded with the primary action, and every part adds value. It efficiently packs key parameter semantics without unnecessary words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple with three parameters and an output schema is present, so return values need not be explained. However, the description lacks usage context and behavioral transparency, making it only minimally complete for an AI agent to invoke confidently.

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 0%, so the description must compensate. It does so effectively by giving concrete protocol examples (NEC, NECext, Samsung32, RC5, RC6, SIRC) and explicitly stating that address and command are hex values with examples (0x04, 0x08). This adds meaning beyond the bare schema types.

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?

The description clearly states the action (transmit) and the resource (infrared signal), and it specifically names the protocol and parameter format. However, it does not differentiate from the sibling tool flipper_ir_universal, which may also transmit IR, so it loses a point for lack of distinction.

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?

No guidance is provided on when to use this tool versus alternatives like flipper_ir_universal. There is no mention of prerequisites, typical scenarios, or exclusions. The description only gives parameter examples, not usage context.

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