Skip to main content
Glama

playlist-play

Control audio for every connected client: play or stop a playlist or one of its sounds, step to the next / previous track, or play a one-off audio file (src) — everywhere, or heard around a point on the scene when x, y and radius are given. action preload with src loads a file on every client ahead of time. Requires bridge module 8.19.0+. EXAMPLES: {"playlistId":"p1"} · {"action":"stop","playlistId":"p1"} · {"src":"sounds/thunder.ogg","volume":0.8}

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": "playlist-play"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNoPositional one-off sound: scene pixels
yNoPositional one-off sound: scene pixels
srcNoAudio file path (from file-list) for a one-off sound
loopNoOne-off sound everywhere: repeat it
actionNoDefault play
radiusNoPositional one-off sound: audible radius in scene distance units (feet)
volumeNoOne-off sound, 0–1
sceneIdNoPositional one-off sound: scene (default: the viewed one)
soundIdNoSound of that playlist (from playlist-list) — play / stop just this sound
playlistIdNoPlaylist ID (from playlist-list)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false. The description adds genuinely non-structured context — that audio fires on every connected client and that a bridge module 8.19.0+ is required — but says nothing about what happens on repeat play/stop, whether tracks overlap, or what the call returns.

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 main clause followed by mode details and three compact JSON examples that anchor the parameter usage. The single long em-dash sentence and the mid-text bridge-version note make it slightly dense, but every element carries information.

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?

For a 10-parameter, all-optional, mode-driven tool with no output schema, the description covers the distinct invocation modes, their triggers, default behavior, and the version prerequisite. Remaining ambiguity (dual-target conflicts, response payload) is minor given annotations already cover the safety profile.

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 100%, so each parameter is documented; the description still earns credit by explaining parameter interaction: x/y/radius jointly trigger positional audio, src+action=preload preloads, and the default action is play. It adds combination semantics the schema cannot express, though it never clarifies what happens if both playlistId and src are supplied.

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?

Opens with a concrete verb+resource ('Control audio for every connected client') and enumerates the operations: play/stop a playlist or single sound, next/previous, one-off src playback. That clearly separates it from playlist-list, playlist-set and playlist-delete without needing their schemas.

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?

Gives explicit mode-selection conditions: everywhere by default, positional when x, y and radius are supplied, and preload when action=preload with src. It does not name a sibling alternative or state when-not to use it (e.g. use playlist-set to edit playlists), so it falls short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources