Skip to main content
Glama
Sign In
OBS MCP

OBS MCP

by Tom-R-Main
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Hybrid

Get Current Scene

obs-get-current-scene
Read-onlyIdempotent

Retrieve the currently active scene name in OBS to identify the live view and trigger automation.

Instructions

Get the current active scene in OBS

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, fully covering the safety profile of this getter. The description adds the 'active' scope qualifier but reveals nothing beyond that—no mention of response shape or studio-mode behavior. It is consistent with annotations, just not additive beyond the name itself.

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?

A single sentence, front-loaded with the key action, with zero wasted words. However, it essentially restates the title verbatim, adding no new information—concise but minimal to the point of being almost purely a paraphrase.

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 zero-parameter read-only getter with rich annotations (readOnly, idempotent, non-destructive) and no output schema, the description is mostly adequate. However, given the sibling obs-get-preview-scene, clarifying that 'active' refers to the program scene (especially relevant in studio mode) would materially improve completeness.

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 and schema coverage is 100% (empty schema). There is nothing for the description to explain, so the baseline of 4 applies. No parameter documentation is needed.

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 states a specific verb ('Get') and resource ('current active scene in OBS'). The word 'active' helps differentiate it from the sibling obs-get-preview-scene, though it does not explicitly name or distinguish itself from sibling tools. This is clear but relies on the reader inferring the distinction.

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. Notably, obs-get-preview-scene exists as a closely related sibling, and the description does not explain the difference between 'active' (program) and 'preview' scenes, nor when an agent should prefer this tool.

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