Skip to main content
Glama

list_audio_inputs

Discover available audio input sources like microphones and desktop audio for OBS Studio configuration.

Instructions

List all audio input sources (mics, desktop audio, etc.).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler logic for the 'list_audio_inputs' tool, which fetches audio inputs and outputs from OBS and formats their mute/volume status.
    case "list_audio_inputs": {
      const { inputs } = await obs.call("GetInputList", {
        inputKind: "wasapi_input_capture",
      });
      // Also grab output captures (desktop audio) — merge both
      const { inputs: outputs } = await obs.call("GetInputList", {
        inputKind: "wasapi_output_capture",
      });
      const all = [...inputs, ...outputs];
      const withMute = await Promise.all(
        all.map(async (input) => {
          const { inputMuted } = await obs.call("GetInputMute", {
            inputName: input.inputName,
          });
          const { inputVolumeMultiplier } = await obs.call("GetInputVolume", {
            inputName: input.inputName,
          });
          return {
            name: input.inputName,
            kind: input.inputKind,
            muted: inputMuted,
            volume: Math.round(inputVolumeMultiplier * 100) / 100,
          };
        })
      );
      return ok({ audio_inputs: withMute });
    }
  • The registration of the 'list_audio_inputs' tool including its description and schema.
    {
      name: "list_audio_inputs",
      description: "List all audio input sources (mics, desktop audio, etc.).",
      inputSchema: { type: "object", properties: {} },
    },
Behavior3/5

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

With no annotations provided, the description carries the full burden of disclosure. It provides examples of what constitutes an audio input (mics, desktop audio) but fails to mention behavioral traits like read-only safety, caching behavior, response format, or what happens when no inputs are available.

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 a single efficient sentence with the action and resource front-loaded. The parenthetical examples add value without excessive length, and there is no redundant or wasted language.

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?

Given the low complexity (zero parameters, no nested objects) and the absence of an output schema, the description adequately covers the tool's function. While mentioning the return format (e.g., array of device names) would be helpful, it is sufficient for agent selection.

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?

Per scoring rules, tools with 0 parameters receive a baseline score of 4. The input schema is empty and the description correctly implies no configuration is needed, requiring no additional parameter semantic clarification.

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 provides a specific verb (List) and resource (audio input sources) with concrete examples (mics, desktop audio). However, it does not explicitly differentiate from the sibling tool `list_sources`, leaving some ambiguity about whether this is a filtered view of sources or a distinct system enumeration.

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?

The description provides no guidance on when to select this tool versus alternatives. Specifically, it does not clarify when to use `list_audio_inputs` versus the sibling `list_sources`, nor does it mention prerequisites like an active session or streaming state.

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/LarsCanGit/OBS-MCP'

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