Skip to main content
Glama
Sign In
OBS MCP

OBS MCP

by Tom-R-Main
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Hybrid

Set Current Scene Collection

obs-set-current-scene-collection
Idempotent

Switch to a specific OBS scene collection by name. Resolves the need to change between preconfigured scene layouts for different production contexts.

Instructions

Switches to a scene collection

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": {
      "sceneCollectionName": "<sceneCollectionName>"
    },
    "name": "obs-set-current-scene-collection"
  }
}

Input Schema

NameRequiredDescriptionDefault
sceneCollectionNameYesName of the scene collection to switch to

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

C2.8/5.0
Behavior2/5

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

Annotations indicate readOnlyHint=false (it mutates state), idempotentHint=true (repeated calls are safe), and destructiveHint=false. The description simply says 'Switches to a scene collection' and does not elaborate on the behavioral implications, such as whether it changes the active collection globally, affects active scenes, or requires specific permissions. The description is consistent with the annotations but does not add extra context that annotations don't already imply.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely short (a single sentence), so it is concise, but it is so minimal that it does not front-load any additional useful details. It could be considered under-specified rather than optimally concise, as it misses opportunities to add context without bloat.

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?

The tool is relatively simple with only one parameter and no output schema, so the description does not need to explain return values. However, given the lack of usage guidelines and behavioral transparency, the description is not complete for an agent to confidently use it. It could mention that the scene collection must already exist, or that switching may affect other scenes.

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?

The input schema includes a description for the sole parameter, 'Name of the scene collection to switch to', which provides clear meaning. The description does not add anything beyond that, so the baseline of 3 applies because the schema already covers it perfectly (100% coverage).

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 clear verb ('Switches to') and specifies the resource ('scene collection'), which is clear. It does not explicitly distinguish this from sibling tools like obs-create-scene-collection or obs-get-scene-collection-list, but the name itself is fairly distinctive.

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?

The description provides no guidance on when to use this tool versus alternatives, such as creating a scene collection or listing existing ones. It does not mention prerequisites, such as the collection needing to exist or being able to switch from the current one. No exclusions or alternative tool references are given.

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