Skip to main content
Glama

obsbot_tail2_audio

Read or set the Tail 2 camera’s audio input volume (0–100) and mute state so recorded or encoded audio matches your needs.

Instructions

Read (bare call) or set the Tail 2's audio input: volume 0-100 and mute. Changes apply to the encoded/recorded audio stream.

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_audio"
  }
}

Input Schema

NameRequiredDescriptionDefault
muteNo
cameraNo
volumeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.9.6
    • removedInput schema / properties / volume / allOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "maximum": 100,
      -    "minimum": 0,
      -    "type": "number"
      -  }
      -]
    • addedInput schema / properties / volume / maximum
      Added value: +100
    • addedInput schema / properties / volume / minimum
      Added value: +0
    • addedInput schema / properties / volume / type
      Added value: +"number"
  2. Addedv0.9.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does add real value by disclosing the effect scope — changes apply to the encoded/recorded audio stream, not merely local monitoring — which is non-obvious. However, it says nothing about permissions, whether settings persist across sessions, or what a bare read returns, leaving significant gaps for a mutation tool.

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?

A single sentence with the read/write split front-loaded and the side-effect note trailing. No redundant restatement of the tool name, no filler, and the volume range is folded in efficiently.

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?

For a 3-parameter mutation tool with no annotations and no output schema, the definition covers mode selection and effect scope but omits the 'camera' parameter and the return behavior of a bare read. It is enough to call the tool in the common case but not enough to call it confidently in a multi-device setup.

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 0%, so the description must compensate and it only partly does. It gives meaning for volume (audio level, 0-100) and mute, but the third parameter 'camera' is never mentioned, so an agent has no idea whether it is required to target a device or optional. Two of three parameters are covered, which is adequate but incomplete.

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 gives a specific verb pair and resource: read or set the Tail 2's audio input, covering volume and mute. It is immediately distinguishable from every sibling, none of which touch audio, though it never explicitly names an alternative. The dual read/write framing is stated up front.

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?

'Read (bare call) or set' tells the agent exactly how to select the two modes: omit arguments to query, supply volume/mute to write. That is clear invocation context. There are no exclusions or preconditions (e.g., whether the device must be streaming), which keeps it below a 5.

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