Skip to main content
Glama
bestimmaa
by bestimmaa

Play an item now in a Roon zone

play_now

Instantly plays a selected album, artist, playlist, or track in your preferred Roon zone, replacing the current queue. Provide a search result key and optionally target a specific zone.

Instructions

Use this when the user wants one specific thing playing right now — an album, artist, playlist, genre mix, or single track (e.g. "play Tycho", "put on In Rainbows", "start some Psytrance in the office", "play that track"). Immediately plays a single search candidate in the target zone and replaces whatever was queued. Pass an itemKey from a recent search_music (or get_tracks_for) result — item keys are session-scoped, so use a fresh one. zoneId is optional: omit it to use ROON_DEFAULT_ZONE, or fall back to the only zone / an "Office" zone / the currently-playing zone; if it still can't decide it returns ZONE_AMBIGUOUS so the agent can ask the user or call list_zones. Optionally shuffle. Returns a PlaybackResult.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
zoneIdNoTarget zone id or output id from list_zones (e.g. an id, or a name substring like 'Office'). Omit to use ROON_DEFAULT_ZONE or fall back automatically.
itemKeyYesWhat to play — item key from a recent search_music or get_tracks_for result (album, artist, playlist, genre, track, etc.).
shuffleNoShuffle the selection when starting playback.
Behavior4/5

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

With no annotations provided, the description carries full burden. It discloses immediate playback, queue replacement, itemKey session scope, zone selection fallback, optional shuffle, and return type. No mention of destructive or rate-limiting behaviors, but core behavioral traits are well covered.

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, well-structured paragraph with no wasted words. Each sentence adds essential information in a logical order: purpose, behavior, parameter details, optionality, and return value.

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 no output schema, the description mentions the return type 'PlaybackResult'. All three parameters are adequately described in the description or schema. The tool's role among siblings is clear. Minor gap: no mention of error cases beyond ZONE_AMBIGUOUS.

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 baseline is 3. The description adds significant value for 'itemKey' (session-scoped, source) and 'zoneId' (fallback logic). 'shuffle' is straightforward. This exceeds the baseline.

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?

The description clearly states the verb ('play now'), specific resource ('a single search candidate in the target zone'), and distinguishes from siblings by emphasizing immediate playback and queue replacement. Examples further clarify the purpose.

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?

The description explicitly says 'Use this when the user wants one specific thing playing right now' and provides examples. It is contrasted with alternatives implicitly via the 'replaces whatever was queued' behavior, but no explicit 'when not to use' is given. The zone fallback logic is clearly explained.

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/bestimmaa/roon-mcp'

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