Skip to main content
Glama
Sign In
OBS MCP

OBS MCP

by Tom-R-Main
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Hybrid

Get Scene Item Enabled

obs-get-scene-item-enabled
Read-onlyIdempotent

Determine if an OBS scene item is enabled using its scene item ID, returning a boolean value to confirm visibility for scene management and automation.

Instructions

Get whether a scene item is enabled

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": {
      "sceneItemId": "<sceneItemId>"
    },
    "name": "obs-get-scene-item-enabled"
  }
}

Input Schema

NameRequiredDescriptionDefault
sceneNameNoName of the scene
sceneUuidNoUUID of the scene
canvasUuidNoUUID of the canvas containing the scene
sceneItemIdYesNumeric ID of the scene item

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A4.1/5.0
Behavior4/5

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

The description states the tool 'gets whether a scene item is enabled', making the read-only behavior clear. The readOnlyHint annotation aligns with this. However, it does not mention possible side effects or the exact response structure.

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 description is one short sentence, which is perfectly concise for a simple getter. The schema is structured clearly with properties and types.

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?

The description lacks context about OBS scene items retrictions (e.g., whether sceneName or sceneUuid is needed, or how to obtain sceneItemId). While the sibling tools provide some context, the description itself is incomplete for a user unfamiliar with OBS API.

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?

Each parameter has a concise description: sceneName as string, sceneUuid as string, canvasUuid as string, and sceneItemId as integer. The required field is clearly indicated. Yet, the descriptions are terse and do not explain relationships or priority among the identifiers.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The tool name and description clearly indicate that it retrieves the enabled status of a scene item in OBS. The purpose is unambiguous and directly stated without extra jargon.

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 is minimal and does not explain how to specify the scene item (e.g., which identifier to use). While the schema indicates sceneItemId is required, it does not clarify when sceneName, sceneUuid, or canvasUuid should be provided, potentially leaving users uncertain.

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