Skip to main content
Glama
Sign In
OBS MCP

OBS MCP

by Tom-R-Main
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Hybrid

Trigger Hotkey by Key Sequence

obs-trigger-hotkey-by-key-sequence
Destructive

Send a hotkey press in OBS Studio by specifying a key sequence and optional modifiers like Ctrl or Shift. Use this tool to trigger custom OBS actions, such as starting recordings or switching scenes, through the MCP server.

Instructions

Triggers a hotkey using a sequence of keys

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "obs-trigger-hotkey-by-key-sequence"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyIdNoThe OBS key ID to use
keyModifiersNoObject containing key modifiers to apply

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already indicate this is a destructive, non-idempotent operation, but the description adds no extra behavioral context. It does not explain side effects, whether keys are pressed and released, how the hotkey sequence is processed, or what happens if the key does not exist. The description contributes almost nothing beyond the structured annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single short sentence with no wasted words, but it provides minimal informational value and largely repeats the tool name. It could use more detail about the key sequence format without being verbose.

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

Completeness2/5

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

For a destructive tool with a nested modifiers object and a clear alternative (trigger by name), a complete description should explain what counts as a sequence, how modifiers combine with keyId, and what side effects occur. The current one-line description is insufficient for an agent to use this tool safely and accurately.

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 description coverage is 100%, with keyId and keyModifiers both documented inline. The description adds no additional parameter meaning beyond the schema, so the baseline score of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says 'Triggers a hotkey using a sequence of keys,' which essentially restates the tool name and title without clarifying what 'key sequence' means or how it differs from the sibling obs-trigger-hotkey-by-name. It names the action and resource but fails to provide a specific, distinguishing definition.

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?

The description gives no guidance on when to use this tool versus obs-trigger-hotkey-by-name or other triggering tools. It does not mention prerequisites, limitations, or typical use cases, so an agent has no context for choosing it over 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