Skip to main content
Glama
Sign In
OBS MCP

OBS MCP

by Tom-R-Main
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Hybrid

Toggle Recording

obs-toggle-record

Start or stop recording in OBS with one toggle command. Detects the current recording status and switches it to the opposite state.

Instructions

Toggles the status of the record output

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-toggle-record"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

B3.2/5.0
Behavior2/5

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

The annotations are all false and uninformative, leaving the description to carry the behavioral burden. 'Toggles the status of the record output' adds little beyond the tool name and does not explain side effects, state transitions, or edge cases (e.g., what happens if recording is in a transitional state). More transparency about the toggle behavior would be expected.

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, clear sentence with no unnecessary words. It perfectly communicates the core action in the most economical way possible.

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, parameterless toggle operation, the description covers the essential action. However, it does not mention return values (e.g., whether it returns the new state) or error conditions. Given the low complexity, this is acceptable but not outstanding—more context about the toggle's effect on the recording state would improve completeness.

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?

With zero parameters, the schema provides complete coverage by definition. The description does not need to explain parameter semantics, and the baseline of 4 is appropriate since there is nothing to add. No further clarification is required.

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 identifies the verb 'toggles' and the resource 'record output', which distinguishes it from sibling tools like obs-start-record and obs-stop-record. However, 'record output' is slightly ambiguous without OBS context and could be interpreted as an audio output rather than the recording state.

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 start-record, stop-record, or toggle-record-pause. The description does not mention that this is a convenient way to toggle the recording state without checking current status, nor does it advise when to prefer start/stop instead.

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