Skip to main content
Glama
LarsCanGit

obs-mcp-server

by LarsCanGit
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Local

stop_recording

Stop recording in OBS Studio to end video capture sessions and save media files.

Instructions

Stop OBS recording.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • obs-mcp-server.js:405-408 (handler)
    The tool handler for "stop_recording" which calls "StopRecord" via the OBS websocket and returns the result.
    case "stop_recording": {
  const result = await obs.call("StopRecord");
  return ok({ recording: false, output_path: result.outputPath ?? null });
}
  • obs-mcp-server.js:84-87 (registration)
    Registration of the "stop_recording" tool in the TOOLS array.
      name: "stop_recording",
  description: "Stop OBS recording.",
  inputSchema: { type: "object", properties: {} },
},

Tool Definition Quality

B3.2/5.0
Behavior2/5

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

With no provided annotations, the description carries the full burden of behavioral disclosure but fails to indicate side effects, idempotency, error conditions (e.g., if called when not recording), or return implications.

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 three-word sentence is front-loaded with zero waste, efficiently conveying the tool's function.

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?

While the basic action is described, the lack of output schema and absence of behavioral details (success/failure states, file saving behavior) leave gaps for a control operation with multiple related siblings.

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?

Zero parameters exist, establishing a baseline of 4. The description appropriately requires no additional parameter clarification.

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 a specific verb ('Stop') and resource ('OBS recording'), clearly distinguishing it from siblings like 'stop_streaming' (different target) and 'start_recording' (opposite action).

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 versus siblings like 'toggle_recording' or prerequisites such as requiring an active recording session.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/LarsCanGit/OBS-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server