Skip to main content
Glama
Sign In
OBS MCP

OBS MCP

by Tom-R-Main
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Hybrid

Get Input Audio Balance

obs-get-input-audio-balance
Read-onlyIdempotent

Retrieve the current audio balance (left/right channel mix) for any OBS input by specifying its name, enabling precise audio adjustments.

Instructions

Gets the audio balance of an input

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": {
      "inputName": "<inputName>"
    },
    "name": "obs-get-input-audio-balance"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputNameYesName of the input to get the audio balance of

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already indicate readOnlyHint=true and destructiveHint=false, so the safety profile is clear. The description adds nothing about runtime behavior (e.g., error conditions, return format), but since the bar is lower with annotations present, a 3 is appropriate for adding no additional behavioral context.

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?

The description is a single sentence, concise and front-loaded. It is not verbose, but it lacks detail. It is efficient, earning a 4.

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

Completeness3/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, no output schema) and the annotations, the description is minimally adequate. However, it provides no context on expected outcome (e.g., range of balance values, meaning of return), which could be important for an agent. It is complete enough for a simple getter but could be improved.

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 100%, so the parameter is well-documented in the schema. The description adds no extra meaning beyond what the schema provides; baseline 3 is warranted.

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

Purpose3/5

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

The description clearly states the tool gets the audio balance of an input, which identifies the verb and resource. However, it does not distinguish this from sibling tools like obs-set-input-audio-balance or obs-get-input-audio-sync-offset; the title already conveys the main purpose, so the description adds little beyond the name.

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

Usage Guidelines2/5

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

No guidance is given on when to use this tool versus alternatives. It does not mention prerequisites (e.g., that the input must exist) or when a user might need this over related tools. The description provides no context for selection.

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