Skip to main content
Glama
Sign In
obs-action-history

obs-action-history

by Giancarlo26
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

obs_stream_control

Start, stop, or query the status of a live stream. Use status freely, but be cautious with start and stop since stopping ends the broadcast for every viewer.

Instructions

Start, stop or query the live stream. Use 'status' freely. Be deliberate with start and stop, because stopping ends the broadcast for every viewer on every platform.

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": {
      "action": "<action>"
    },
    "name": "obs_stream_control"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations, the description reveals a critical behavioral consequence: stopping ends the broadcast for all viewers on every platform. This is essential safety information beyond what the schema provides, making the impact of actions transparent.

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?

Two crisp sentences deliver purpose, usage caution, and behavioral impact. Every word carries weight; it's front-loaded with the action and immediately provides the key warning.

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?

Given the tool's simplicity (one parameter), the description fully covers what the tool does, when to use it carefully, and the main side effect. No gaps remain for an agent to misuse the tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single 'action' parameter is an enum without a description in the schemaudder. The description adds meaning by clarifying what each action does (start, stop, status) and emphasizes the caution around stop, thus compensating fully for low schema coverage.

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 states the tool starts, stops, or checks status of a live stream. It uses a specific verb and resource, and clearly distinguishes from siblings like obs_record_control or obs_output_control by focusing on the broadcast stream.

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

Usage Guidelines4/5

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

It provides clear guidance: use 'status' freely but be deliberate with start/stop due to impact. It doesn't explicitly mention alternatives or when not to use, but the context of 'deliberate' implies caution. Sibling names suggest other control tools, but no explicit comparison is given.

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