Skip to main content
Glama
Sign In
streamdeck-mcp

streamdeck-mcp

by hugoacfs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

streamdeck_create_action

Create an executable shell script in ~/StreamDeckScripts and return a native Open action block so a Stream Deck button can run the command when pressed.

Instructions

Create an executable shell script in ~/StreamDeckScripts and return a native Open action block for it.

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": {
      "name": "<name>",
      "command": "<command>"
    },
    "name": "streamdeck_create_action"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesHuman-readable action name used for the script filename and button label.
commandYesShell command to run when the button is pressed.
filenameNoOptional override for the script filename.
working_directoryNoOptional working directory to cd into before executing the command.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.7/5.0
Behavior2/5

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

No annotations are provided, so the description must carry full behavioral transparency. It mentions file creation and return value but omits details like overwrite behavior, permission requirements, or error handling.

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, well-structured sentence that conveys the essential information without any redundant 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 description provides basic functionality but lacks details on return value format, prerequisites, or error scenarios. Given missing annotations and no output schema, more context would help.

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 is 3. The description adds value by explaining that 'name' is used for both filename and button label, which is not in the schema. However, it does not mention the optional parameters like 'filename' and 'working_directory'.

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 tool creates an executable shell script in ~/StreamDeckScripts and returns a native Open action block. It distinguishes from siblings like streamdeck_create_icon and streamdeck_read_page by specifying the exact output and location.

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?

The description implies usage for creating action buttons with shell commands, but lacks explicit guidance on when to use this tool versus alternatives or when not to use it.

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