Skip to main content
Glama

now_playing

Retrieve currently playing track details across all Sonos devices, including track name, artist, and album, for real-time monitoring and management.

Instructions

Retrieve information about currently playing tracks on all Sonos devices.

Returns: List[Dict[str, str]]: A list of dictionaries containing the name, title, artist, and album of currently playing tracks.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The core handler function for the 'now_playing' MCP tool. Decorated with @mcp.tool() for automatic registration using FastMCP. It discovers Sonos devices, checks which are playing, and returns a list of dicts with device name, title, artist, and album for currently playing tracks.
    @mcp.tool()
    def now_playing() -> List[Dict[str, str]]:
        """Retrieve information about currently playing tracks on all Sonos devices.
        
        Returns:
            List[Dict[str, str]]: A list of dictionaries containing the name, title, artist, and album of currently playing tracks.
        """
        devices = get_devices()
        infos = []
        for device in devices.values():
            track = device.get_current_track_info()
            if not track:
                continue
            is_playing = device.get_current_transport_info()["current_transport_state"] == "PLAYING"
            if is_playing:
                infos.append({
                    "name": device.player_name,
                    "title": track["title"],
                    "artist": track["artist"],
                    "album": track["album"]
                })
        return infos
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states the tool retrieves information (implying read-only) and describes the return format, but lacks details on behavioral traits such as error handling, rate limits, authentication requirements, or whether it requires specific device states. For a tool with zero annotation coverage, this is a significant gap.

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 front-loaded with the core purpose in the first sentence, followed by a clear specification of the return value. Every sentence adds value without redundancy, making it efficient and well-structured for an AI agent.

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?

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is adequate but has gaps. It explains what the tool does and the return format, but lacks context on usage guidelines and behavioral transparency, which are important for a tool in a crowded sibling set with potential overlaps.

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 has 0 parameters, and schema description coverage is 100%, so no parameter information is needed. The description appropriately focuses on the tool's function and output without unnecessary parameter details, meeting the baseline for zero parameters.

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 clearly states the tool's purpose: 'Retrieve information about currently playing tracks on all Sonos devices.' It specifies the verb ('Retrieve'), resource ('currently playing tracks'), and scope ('all Sonos devices'). However, it doesn't explicitly differentiate from sibling tools like 'get_current_track_info' or 'get_all_device_states', which likely have overlapping functionality.

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 use this tool versus alternatives. It doesn't mention prerequisites, timing considerations, or how it differs from similar tools like 'get_current_track_info' or 'get_all_device_states'. The agent must infer usage from the description alone.

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

Related 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/WinstonFassett/sonos-mcp-server'

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