Skip to main content
Glama
Sign In
OBS MCP

OBS MCP

by Tom-R-Main
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Hybrid

Stop Replay Buffer

obs-stop-replay-buffer
Idempotent

Terminate the active replay buffer in OBS, saving the recent clip and halting further capture.

Instructions

Stops the replay buffer 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-stop-replay-buffer"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

B3.3/5.0
Behavior2/5

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

Annotations declare idempotentHint=true but destructiveHint=false. The description is very brief and doesn't disclose behavioral consequences beyond stopping output. It doesn't mention that stopping the buffer may discard the buffered content unless saved first (which is implied by siblings like obs-save-replay-buffer). It also doesn't state whether this affects other outputs. The description adds minimal value beyond the annotations.

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, concise sentence that directly states the purpose. It's front-loaded and contains no unnecessary words, effectively communicating the tool's function without filler.

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?

Given the tool is a simple action (no params, no output schema), the description is brief but lacks context about the tool's effect in the broader workflow. It doesn't explain the relationship to saving the replay buffer or potential data loss, which would be useful in the context of OBS replay buffer management. With no annotations covering these aspects, the description should have offered more.

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?

The tool has 0 parameters, and schema description coverage is 100% (empty schema means no parameters to document). The description doesn't need to explain parameters, and a baseline of 4 is appropriate for a no-parameter tool that is adequately described.

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 'Stops the replay buffer output' clearly states the action (stop) and the resource (replay buffer). It distinguishes from sibling tools like obs-start-replay-buffer and obs-toggle-replay-buffer by specifying the stopping action, though it could be more explicit about the context (e.g., stopping recording to a buffer for future saving).

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 when the replay buffer is active, but doesn't explicitly state when to use this vs. obs-save-replay-buffer or obs-stop-record. It doesn't mention prerequisites like having a running replay buffer or that stopping may discard unsaved content. It could better differentiate from related stop/save tools.

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