Skip to main content
Glama

obsbot_tail2_stream_config

Read or set the shared stream encoder configuration—H.264/H.265, resolution, and bitrate—for both network outputs, and retrieve RTSP URLs; disable live output before changing resolution.

Instructions

Read (bare) or set the stream encoder configuration shared by the network outputs: encoder (h264/h265), resolution (camera format like 1920X1080P30), bitrate (Mbps). The bare read also includes the RTSP URLs for both network interfaces. GATED (MEASURED 2026-10-01): resolution writes 500 while an output is live — set obsbot_tail2_stream output:"off" first (encoder and bitrate writes are ungated). Readback-verified writes.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "obsbot_tail2_stream_config"
  }
}

Input Schema

NameRequiredDescriptionDefault
cameraNo
bitrateNo
encoderNo
resolutionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.9.6
    • removedInput schema / properties / bitrate / allOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "maximum": 160,
      -    "minimum": 0.7,
      -    "type": "number"
      -  }
      -]
    • addedInput schema / properties / bitrate / maximum
      Added value: +160
    • addedInput schema / properties / bitrate / minimum
      Added value: +0.7
    • addedInput schema / properties / bitrate / type
      Added value: +"number"
  2. Addedv0.9.2

TDQS

A4.3/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so unusually well: it discloses the gated write behavior with the exact failure (HTTP 500 while an output is live), the prerequisite remedy, which writes are ungated, that writes are readback-verified, and that the bare read returns RTSP URLs for both interfaces. That is exactly the behavioral context an agent cannot get from 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the purpose, then fields, then the read-only extra, then the gating caveat — a sensible priority order. Dense but nearly every clause carries information; only the parenthetical '(bare)' and '(MEASURED 2026-10-01)' add mild noise.

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

Completeness4/5

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

For a 4-parameter mutation tool with no annotations and no output schema, the definition covers read semantics, write gating, and verification. The main gap is the undocumented camera parameter and nothing about what a set call returns, but the core operational picture is complete.

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

Parameters3/5

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

Schema coverage is 0%, so the description must compensate. It explains encoder values, gives a concrete resolution example matching the schema pattern, and states bitrate units (Mbps) — but the camera parameter is never mentioned, and the 0.7–160 bitrate bounds are left to the schema.

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?

Names the exact resource (stream encoder configuration shared by the network outputs) and the specific fields it covers (encoder, resolution, bitrate), and distinguishes the bare-read mode from the write mode in the first sentence. An agent can tell this apart from obsbot_tail2_stream, which it explicitly references as a related but separate control.

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?

Gives a concrete when-to-use rule: set resolution only after turning obsbot_tail2_stream output:off, and notes that encoder/bitrate writes are ungated. This is actionable and grounded in a measured failure, though it doesn't explicitly frame when to prefer this tool over obsbot_tail2_stream for output control generally.

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