Skip to main content
Glama
Sign In
OBS MCP

OBS MCP

by Tom-R-Main
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Hybrid

Toggle Output

obs-toggle-output

Toggle any OBS output on or off by name, such as streaming or recording, to start or stop it without manual control.

Instructions

Toggles the status of an output

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": {
      "outputName": "<outputName>"
    },
    "name": "obs-toggle-output"
  }
}

Input Schema

NameRequiredDescriptionDefault
outputNameYesOutput name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

C2.9/5.0
Behavior2/5

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

The annotations already convey readOnlyHint=false and idempotentHint=false, and the description only restates 'toggles' without adding behavioral context such as what 'status' means, what side effects occur, or whether it toggles between specific states. It adds minimal value 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.

Conciseness4/5

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

The description is a single, short sentence with no wasted words, making it very concise. It is front-loaded with the action verb, but the brevity also contributes to vagueness about what 'status' entails.

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?

For a simple one-parameter tool with no output schema, the description is minimally adequate. However, it fails to clarify what 'toggling status' means in practice, and the presence of sibling start/stop/get-status tools suggests more context would help an agent invoke it correctly.

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% for the single outputName parameter, so the schema fully documents it. The description does not add any additional meaning about the parameter's format, constraints, or relationship to the tool's behavior, matching the baseline for high schema coverage.

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 uses the specific verb 'Toggles' and identifies the resource as 'the status of an output', clearly distinguishing it from toggles for other entities like record, stream, or virtual cam. However, 'status' is vague and does not specify what state changes (e.g., started/stopped), leaving slight ambiguity even with sibling context.

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 given for when to use this tool versus alternatives like obs-start-output, obs-stop-output, or obs-get-output-status. With many sibling toggle tools, the description provides no exclusions or context for selection.

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