Skip to main content
Glama

diagnose_av_health

Diagnose stream or recording stuttering by analyzing key OBS performance ratios to pinpoint if the cause is render overload, encoder lag, or network congestion, with targeted fixes for each.

Instructions

Diagnose why a stream/recording might be dropping frames or stuttering — pulls GetStats + GetStreamStatus + GetRecordStatus in one call and interprets the ratios instead of leaving the AI to fetch three things and do the arithmetic itself.

The three numbers that actually matter, and what each one means:

  • renderSkippedFrames/renderTotalFrames high: OBS's render thread can't keep up with your scene (too many sources/filters, canvas resolution too high, or GPU-bound). Fix: lower canvas resolution, cut filters, simplify the scene.

  • outputSkippedFrames/outputTotalFrames high with LOW congestion: encoding can't keep up (CPU/GPU encoder overloaded). Fix: switch to a hardware encoder (NVENC/AMF/QSV), lower the encoder preset, or lower output resolution/fps.

  • outputCongestion high: the network can't keep up with your bitrate. Fix: lower bitrate, check upload speed.

These thresholds are heuristics, not authoritative OBS cutoffs — a few skipped frames right after starting a stream is normal; this flags sustained skip ratios worth investigating, not noise.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

With no annotations provided, the description carries the full burden. It discloses that the tool internally pulls three API endpoints, interprets specific ratios, and flags sustained issues heuristically rather than authoritative cutoffs. It also warns that a few skipped frames after start is normal, providing valuable behavioral context beyond what a schema could convey.

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 front-loaded with a one-sentence purpose, followed by a structured breakdown of the three key ratios and their meaning, plus concise fix suggestions. Every sentence contributes useful information, and the heuristic caveat at the end is relevant and concise.

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 interpretive complexity, the description covers what the tool does, why it exists (to avoid manual arithmetic), how to interpret each ratio, practical fixes, and the heuristic nature of thresholds. There is no output schema, but the description provides the necessary interpretive context for the agent to act on the result.

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?

The input schema has zero parameters, so the baseline is 4. There are no parameter semantics to elaborate, and the description appropriately focuses on the tool's interpretation logic instead of parameters.

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 starts with a specific verb and resource: 'Diagnose why a stream/recording might be dropping frames or stuttering'. It clearly distinguishes itself from sibling raw-getter tools by stating it aggregates GetStats + GetStreamStatus + GetRecordStatus and interprets the ratios rather than just fetching data.

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?

It explicitly frames when to use the tool: when a stream/recording is dropping frames or stuttering, and contrasts it with the alternative of fetching three separate pieces of data and doing arithmetic. The included fixes for each scenario guide the agent toward next actions, and the heuristic caveat prevents over-triggering on normal noise.

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/xDarkzx/OBS_MCP'

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