Skip to main content
Glama
Sign In
OBS MCP

OBS MCP

by Tom-R-Main
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Hybrid

Set Preview Scene

obs-set-preview-scene
Idempotent

Set the preview scene in OBS to the named scene, letting you check it before switching.

Instructions

Set the current preview scene in OBS Studio Mode

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": {
      "sceneName": "<sceneName>"
    },
    "name": "obs-set-preview-scene"
  }
}

Input Schema

NameRequiredDescriptionDefault
sceneNameYesThe name of the scene to set as preview

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?

Annotations indicate idempotentHint=true, so the tool is safe to call multiple times without side effects. However, the description doesn't add context beyond this, such as whether the tool has any effect when studio mode is off, or whether it requires specific permissions. No annotations contradiction, but the description could add more behavioral context.

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 exceptionally concise—one sentence with no wasted words. It front-loads the action and resource clearly.

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 100% schema coverage and idempotentHint, the description is adequate but doesn't explain return values or side effects. It's complete enough for a straightforward setter, but could benefit from mentioning studio mode requirement.

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%, and the parameter 'sceneName' is sufficiently described in the schema ('The name of the scene to set as preview'). The description adds minimal value beyond the schema, but since coverage is high, baseline 3 is appropriate.

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 states the action (set) and the target resource (preview scene) in OBS Studio Mode. It distinguishes itself from related tools like obs-set-current-scene and obs-trigger-studio-transition by specifying 'preview' scene, though it doesn't explicitly contrast with siblings.

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 in 'OBS Studio Mode' but doesn't explain when to use this instead of obs-set-current-scene or when preview mode must be enabled. It doesn't mention prerequisites like studio mode being active, or when not to use it.

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