Skip to main content
Glama

Play a local audio file

play_audio
Read-onlyIdempotent

Plays a local audio file through the system’s default output device; supports WAV, MP3, M4A, AAC, OGG, and FLAC.

Instructions

Play a local audio file through the system's default output device. Supports WAV, MP3, M4A, AAC, OGG, FLAC.

Args: input_file_path (str): Absolute path or relative to SONILO_MCP_BASE_PATH.

Returns: Success message including the played path.

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": {
      "input_file_path": "<input_file_path>"
    },
    "name": "play_audio"
  }
}

Input Schema

NameRequiredDescriptionDefault
input_file_pathYes

Output Schema

NameRequiredDescriptionDefault
textYes
typeYes
_metaNo
annotationsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the description only needs to add beyond that — and it does: the output device used, the exact set of accepted container formats, and how relative paths resolve. It stops short of saying whether playback blocks until completion or returns immediately, which matters for sequencing.

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?

Front-loaded with the core action, then compact Args/Returns sections. The Returns block is minor redundancy since an output schema exists, but it costs only one line.

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?

For a single-parameter tool with annotations and an output schema, the essentials are covered: accepted formats, path resolution, and target device. The one meaningful hole is synchronous-vs-asynchronous playback behavior, which an agent needs to know before chaining a follow-up call.

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?

Schema coverage is 0%, so the description carries the load and delivers: input_file_path is an absolute path or relative to SONILO_MCP_BASE_PATH, a resolution rule absent from the schema. It doesn't mention extension requirements or what happens when the path is a directory or missing.

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?

States a specific verb and resource: play a local audio file through the system's default output device, plus an enumerated list of supported formats. That resource (playback of an existing file) is unmistakably distinct from every sibling, which are all generation/analysis tools.

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?

Usage is only implied by the verb 'play' — nothing states when to reach for this versus the generation siblings, nor any prerequisite such as the file needing to already exist. No exclusions or alternatives are named, though in this toolset the alternative set is far enough away that the risk is low.

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