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

obs-action-history

by Giancarlo26
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

obs_audio_routing_map

Check every audio input's tracks, monitoring, sync offset, and balance, then get a list of misrouted sources that need correction.

Instructions

The whole audio routing picture in one call: every input that carries audio, with its tracks, monitoring, sync offset and balance, and an explicit list of what is misrouted. Read-only. Start here when audio is wrong and you do not yet know which source is at fault - the alternative is four requests per input, and the answer is usually a comparison between sources rather than a fact about one of them. It names the failures that a level meter cannot show you: sources on no track (inaudible AND unmeterable), sources off track 1 (they meter but never reach the stream or the recording on the reference machine), monitoring left enabled (doubled, out-of-phase audio via the room microphone), sync offsets stored past the ~960 ms cap where OBS applies nothing, and balances pushed off centre. Inputs with no audio at all are skipped rather than listed as errors.

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

Input Schema

NameRequiredDescriptionDefault
onlyProblemsNotrue = return only inputs with at least one note. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations provided, the description carries full behavioral burden and succeeds: it states 'Read-only', lists specific failure classes it detects, notes that no-audio inputs are skipped rather than flagged, and describes edge cases like sync offsets past ~960 ms. This is far beyond a generic read-only label.

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 longer than usual but every clause earns its place; it front-loads the core purpose and then details failure modes. Minor redundancy between 'explicit list of what is misrouted' and the subsequent list of failures, but overall it is well-structured and readable.

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?

Despite no output schema and no annotations, the description tells the agent what the tool returns, which input categories are included, which are skipped, the specific misrouting conditions detected, and when to prefer it over alternatives. This is unusually complete for a diagnostic tool.

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?

The input schema already covers the only parameter (onlyProblems) with a clear description and default. The tool description adds no parameter-specific semantics beyond the schema, so the baseline score of 3 applies.

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 a specific, valuable function: 'The whole audio routing picture in one call' with explicit outputs (tracks, monitoring, sync offset, balance, misrouted list). It also clearly differentiates from alternatives by framing this as the aggregate diagnostic versus per-input requests.

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?

The description gives explicit when-to-use guidance: 'Start here when audio is wrong and you do not yet know which source is at fault.' It also names the alternative ('four requests per input') and explains why this tool is preferred for comparison-driven diagnosis, making the usage context clear.

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