Check whether a scene item in OBS Studio is enabled or visible by retrieving its state. Use this to confirm item visibility before making changes.
Gets the enable/visibility state of a scene item
| Name | Required | Description | Default |
|---|---|---|---|
| sceneName | No | Name of the scene the item is in | |
| sceneUuid | No | UUID of the scene the item is in | |
| sceneItemId | Yes | Numeric ID of the scene item |
Changes observed during successful MCP inspections.
v1.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the behavioral burden. 'Gets' implies a safe read operation, and the description correctly frames the tool as retrieving state rather than changing it, but it does not explicitly state that it is read-only, whether it has side effects, or what happens with invalid scene item IDs.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence with no unnecessary wording. It communicates the core operation immediately and contains no filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple getter with fully described parameters, the description is minimally adequate. However, because there is no output schema, it could usefully state that the result is a boolean enabled/visibility value; as written, the return behavior is only implied.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the input schema already documents all three parameters. The description adds only the general concept of a scene item's enable/visibility state and does not clarify how sceneName, sceneUuid, and sceneItemId relate or interact beyond what the schema provides.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description gives a specific verb and resource: 'Gets the enable/visibility state of a scene item.' This clearly distinguishes it from mutating siblings such as obs-set-scene-item-enabled, though it does not explicitly name any sibling as an alternative.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description offers no guidance on when to use this tool versus alternatives. It implies a read operation, but does not mention prerequisites, when to prefer it over obs-get-scene-item-locked or obs-get-scene-items, or any exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.