Skip to main content
Glama
Sign In
OBS MCP

OBS MCP

by Tom-R-Main
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Hybrid

Set Current Scene

obs-set-current-scene
Idempotent

Switches OBS to a specified scene by name, making it the active scene for live output and control.

Instructions

Set the current active scene in OBS

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-current-scene"
  }
}

Input Schema

NameRequiredDescriptionDefault
sceneNameYesThe name of the scene to set as current

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already convey that this is a mutating, non-destructive, idempotent operation. The description correctly aligns with those annotations and adds the nuance of 'current active scene', but it does not disclose error behavior (e.g., invalid scene name) or side effects beyond the state change. No contradiction.

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?

A single, front-loaded sentence that states the verb and target with no filler. It is appropriately minimal for a simple setter tool.

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 full schema coverage and safety annotations, the description is mostly adequate. It is incomplete because it omits the important relationship to preview scene / studio mode and does not mention that valid scene names must come from an existing scene (e.g., via obs-get-scene-list).

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 coverage is 100%, and the sceneName parameter is already described as 'The name of the scene to set as current'. The description adds no extra meaning about parameter source, exactness, or relation to obs-get-scene-list, so it does not go beyond the schema.

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 ('Set') and resource ('current active scene in OBS'), and 'active' helps distinguish it from the sibling obs-set-preview-scene. However, it does not explicitly contrast it with preview-scene or studio-mode behavior, so it stops short of full differentiation.

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 about when to use this tool versus alternatives. Given the sibling obs-set-preview-scene, the agent may not know that 'current active scene' means the program scene and that in studio mode there is a separate preview scene. Prerequisites like the scene needing to exist are also absent.

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