Retrieve recent OBS Studio events from the real-time ring buffer, with optional limit and event-type filtering, to inspect scene, audio, or recording activity.
Get recent OBS events captured in the real-time circular ring buffer
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of recent events to return (default 20, max 100) | |
| eventType | No | Filter events by type substring (e.g., 'SceneChanged', 'MuteStateChanged') |
Changes observed during successful MCP inspections.
v1.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full behavioral burden. The phrase 'circular ring buffer' hints that results are bounded and oldest events are overwritten, but the buffer capacity, retention window, or whether events are consumed on read are never stated. Nothing is said about non-destructiveness, ordering, or return shape for a tool whose whole value depends on that semantics.
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?
A single front-loaded sentence with no filler, and the resource and buffer mechanism appear immediately. It is efficient, though the brevity comes at the cost of the behavioral detail noted elsewhere.
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 tool with no annotations, no output schema, and a stateful ring-buffer source, the description should disclose buffer size, event object shape, and ordering. None of that is present, so an agent cannot predict what it will receive or how far back 'recent' reaches.
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 both limit (default 20, max 100) and eventType (substring filter) are already fully documented. The description adds no additional meaning such as case sensitivity or matching behavior, so the baseline of 3 for schema-documented parameters applies.
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?
States a specific verb and resource ('Get recent OBS events') plus the mechanism ('real-time circular ring buffer'), so an agent knows this is a read of recent event history rather than a status call. It does not, however, differentiate itself from related siblings such as obs-broadcast-custom-event or explain how 'recent' differs from a live subscription.
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?
There is no guidance on when to call this versus obs-get-status, obs-broadcast-custom-event, or obs-get-stats, and no mention of polling cadence or whether the buffer must be drained. The sentence is purely descriptive, leaving the agent to infer usage context entirely.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.