Skip to main content
Glama

list_audio_sources

Read-onlyIdempotent

Lists apps currently using audio along with the default microphone and output, helping you choose the correct source for call recording.

Instructions

Apps currently using audio (to choose the source), and the default microphone and output.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile needs no restatement. The description adds essentially no behavioral context: it does not say whether apps must be actively playing audio to appear, whether devices are enumerated or only defaults, or how often results change. With annotations covering safety, this remains thin.

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?

A single compact sentence with no filler, and the key distinction (current audio-using apps vs. default devices) is front-loaded. It is slightly elliptical — the missing verb makes the first few words require re-reading — but nothing is wasteful.

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?

With an output schema present and no parameters, the description need not explain return values, and it roughly gestures at them. But for a discovery tool meant to feed start_recording, it omits the one piece of context an agent needs: that this is the selection step preceding capture. Output schema lowers the bar, so a 3 is fair.

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 tool takes zero parameters, so the baseline is 4. There is nothing for the description to disambiguate on the input side.

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 is a noun phrase listing returned contents ('Apps currently using audio ... and the default microphone and output') rather than a verb-led statement of what the tool does. The resource is identifiable and distinct from recording siblings, but the action ('list/enumerate available audio sources') must be inferred from the name. Adequate but not explicit.

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

Usage Guidelines3/5

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

The parenthetical '(to choose the source)' implies the intended workflow — pick an input before starting a recording — but never names start_recording or any sibling as the follow-up. There is no explicit when-to-use / when-not statement, only an implied context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.