Skip to main content
Glama
Giancarlo26

obs-action-history

by Giancarlo26

obs_projector_open_source

Open a projector to display a single source (input or scene) alone, routing that picture to a monitor or capture card without re-encoding.

Instructions

Open a projector showing ONE source on its own, rather than the whole mix. sourceName takes a scene name as readily as an input name - in OBS a scene is a source - so this projects either a single camera, screen capture or media input, or an entire scene composed as it would look on air.

What it is for: feeding one specific picture to hardware or to a person. A guest's camera on a monitor they can see, one screen share to a capture card, a scene routed to a second machine - all without re-encoding anything, because the projector is just the same frames drawn to a window.

A source projector shows that source ALONE. Overlays that live in a different scene are not in it: on the reference machine the HUD is its own scene added into the others, so projecting a camera source gives you the bare camera, and projecting a scene gives you that scene's own composite. If you want what the audience sees, that is the program mix, not a source - use obs_projector_open_mix.

Defaults to a WINDOW. obs-websocket cannot close or enumerate projectors - this window stays until someone closes it in the OBS UI.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
canvasUuidNoUUID of the canvas the source belongs to, when disambiguating by name.
sourceNameNoName of the input OR scene to project.
sourceUuidNoUUID instead of a name.
monitorIndexNoIndex from obs_monitor_list for fullscreen. Omit, or use -1, for a normal window. Mutually exclusive with projectorGeometry.
projectorGeometryNoSize and position for a windowed projector, in Qt's base64 geometry format. The protocol does not document how to construct one; omit it unless you are reusing a known value.
Behavior5/5

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

No annotations are provided, so the description carries the full burden. It discloses that the projector defaults to a window, that obs-websocket cannot close or enumerate projectors, that it shows only the source alone (overlays from other scenes are excluded), and that it does not re-encode. These are key behavioral details beyond the schema.

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 well-structured with clear paragraphs, each serving a distinct purpose: the core action, use cases, behavioral nuances, and limitations. Every sentence adds value without redundancy, balancing detail and brevity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 5 parameters and no output schema, the description covers essential context: the distinction between sources and scenes, the practical use cases, the exclusion of overlays, the window behavior, and the alternative for the program mix. It is complete enough for an agent to decide when and how to call it.

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?

Schema coverage is 100%, so baseline is 3. The description adds meaning by explaining that sourceName accepts scene names as readily as input names, and provides guidance on projectorGeometry ('omit it unless you are reusing a known value') and monitorIndex ('Omit, or use -1, for a normal window'). These clarifications exceed the schema's descriptions.

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 description clearly states the tool's purpose: 'Open a projector showing ONE source on its own, rather than the whole mix.' It explicitly distinguishes from obs_projector_open_mix and explains that sourceName can be a scene or input, making the scope unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit use cases ('feeding one specific picture to hardware or to a person') and a clear alternative: 'If you want what the audience sees, that is the program mix, not a source - use obs_projector_open_mix.' This provides both when-to-use and when-not-to-use guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Giancarlo26/obs-action-history'

If you have feedback or need assistance with the MCP directory API, please join our Discord server