Skip to main content
Glama

OBS bitrate and stream settings

get_stream_settings
Read-onlyIdempotent

Recommend OBS output settings for live streaming: video bitrate, audio bitrate, rate control, keyframe interval, resolution, frame rate and encoder preset, based on the platform's published recommendations, how much motion the content has and the user's upload speed. Warns when the upload speed or the platform cap forces a lower bitrate.

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": "get_stream_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
fpsNo
motionNolow: Just Chatting, art, strategy; normal: most games; high: shooters, racing.normal
encoderNonvenc (NVIDIA), amf (AMD), qsv (Intel), x264 (CPU), apple (Apple VT).nvenc
platformNo"other" means another platform or local recording.twitch
resolutionNoOutput height in pixels.
upload_mbpsNoMeasured upload speed in Mbps.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuine behavioral context the annotations cannot: the recommendation is derived from platform published caps, content motion, and upload speed, and it emits a warning when the upload speed or platform cap forces a lower bitrate. It stops short of describing the shape of the returned settings or warning, which matters given there is no output 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?

Two sentences, no filler, with the core answer (what settings are returned) front-loaded. The enumerated output list is long but each item earns its place by telling the agent what to expect. Minor cost: the second sentence's warning behavior could be tightened, but nothing is redundant.

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 six-parameter, all-optional, read-only advisory tool with no output schema, the description covers the inputs consulted, the outputs produced, and the failure/warning condition. The main gap is the return shape: with no output schema, the agent cannot tell whether it gets a structured settings object, a prose recommendation, or a warning string alongside it. Overall it is sufficient to invoke correctly.

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 description coverage is 83% and five of six parameters are enums, so the schema already carries most semantics; baseline 3 applies. The description conceptually names motion and upload speed as drivers of the result, which adds a little meaning. However, it slightly muddies the input model by listing resolution, frame rate and encoder preset as things the tool 'recommends' when they are actually supplied as inputs, leaving the agent to guess whether those are user-supplied constraints or computed outputs.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource ('Recommend OBS output settings') and enumerates exactly what is produced: video bitrate, audio bitrate, rate control, keyframe interval, resolution, frame rate, encoder preset. That is far more informative than the name 'get_stream_settings', which misleadingly suggests a simple fetch. It does not explicitly distinguish itself from the nearest sibling (create_obs_widget), so it falls short of a 5.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the agent can infer this is for sizing a live stream on a given platform, and the mention of 'local recording' under the platform enum hints at non-stream use. There is no explicit when-to-use/when-not-to-use framing and no statement of prerequisites, such as needing a measured upload speed first.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources