Skip to main content
Glama
Sign In
OBS MCP

OBS MCP

by Tom-R-Main
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Hybrid

Resume Recording

obs-resume-record
Idempotent

Resume a paused recording in OBS Studio to continue capturing your stream or video without starting a new file.

Instructions

Resumes 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-resume-record"
  }
}

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?

The description 'Resumes the record output' adds no behavioral detail beyond what the annotations already imply (mutating, idempotent, non-destructive). It doesn't disclose what happens if called when not paused (no-op, error, etc.), which would add value. Since annotations exist, the bar is lower, but no extra context is provided.

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 one-sentence description 'Resumes the record output' is perfectly sized for a zero-parameter action. It's entirely free of fluff and front-loads the action, making it easy to parse.

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 tool this simple, the description is nearly complete—it states the action unambiguously and needs no parameter or return-value documentation. However, it would benefit from a brief note on preconditions (e.g., 'only effective when recording is paused') to make it fully self-contained.

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 zero parameters, so there's no parameter semantics for the description to elaborate on. The schema is fully complete at 100% coverage, earning the baseline score of 4 for no-parameter tools.

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 'Resumes the record output' uses a specific verb (resumes) and resource (record output), making the tool's function immediately understandable. While it's not a tautology—it clarifies the action on the recording output—it doesn't explicitly contrast with similar siblings like obs-start-record or obs-toggle-record.

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 on when to use this tool versus alternatives like obs-pause-record or obs-stop-record. The description doesn't mention prerequisites (e.g., 'use after pausing') or exceptions, leaving the agent without explicit direction on tool 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