Skip to main content
Glama
Sign In
OBS MCP

OBS MCP

by Tom-R-Main
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Hybrid

Toggle Input Mute

obs-toggle-input-mute

Toggle the mute state of any audio input in OBS Studio by specifying its name. Use this tool to quickly mute or unmute a source during live production or recording without interrupting your workflow.

Instructions

Toggles the audio mute state of an input

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": {
      "inputName": "<inputName>"
    },
    "name": "obs-toggle-input-mute"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputNameYesName of the input to toggle the mute state of

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already communicate that this is not read-only, not idempotent, and not destructive. The description adds the domain and behavior of flipping the mute state, but it does not explain error conditions, return behavior, or that repeated calls alternate the state.

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 one short, direct sentence. It contains no redundant phrasing or filler and places the action and resource at the center.

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 single-parameter tool with strong annotations and full schema coverage, the description is nearly complete. It lacks sibling guidance and any note about behavior when the input does not exist, but those gaps are minor given the tool's low complexity.

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%, so the single inputName parameter is already documented. The description adds no deeper semantic meaning about how the name must match an existing OBS input, but it also does not need to compensate for missing schema detail.

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 states a specific action and resource: toggling the audio mute state of an input. It clearly distinguishes from sibling tools like obs-get-input-mute and obs-set-input-mute by signaling a flip rather than a read or set operation.

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?

There is no guidance about when to use this tool instead of obs-get-input-mute or obs-set-input-mute, nor any mention that the input must already exist. The agent is left to infer the usage from the verb 'toggle'.

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