Skip to main content
Glama
Golden Hour Selector

Golden Hour Selector

by neleus-agent

list_devices

Lists available Spotify Connect devices with names, types, active status, and volume. Use it to discover device names, such as linked Sonos rooms, before playing or transferring playback.

Instructions

List the available Spotify Connect devices (id, name, type, is_active, volume_pct). Use to discover device names — e.g. linked Sonos rooms — before playing or transferring to one.

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_devices"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations exist, so the description carries the full behavioral burden and it only partially does so: it discloses the returned fields (id, name, type, is_active, volume_pct), implying a read-only discovery call. It says nothing about whether unreachable/offline devices are included, whether discovery is cached or slow, or whether authentication or an active playback session is required.

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?

Two sentences, zero waste: the resource and its return fields are front-loaded, then the usage guidance follows. Nothing is repeated from the name or title.

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?

With no annotations, no parameters, and no output schema, the description does the necessary work by listing exactly which fields come back and what the call is for. The remaining gap is behavioral context around device availability and timing, which matters for a network-discovery style 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?

The tool takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description appropriately spends its words on the return shape instead.

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 opens with a specific verb plus a distinct resource ("List the available Spotify Connect devices") and enumerates the returned fields, which cleanly separates it from playlist- and playback-oriented siblings. An agent knows immediately this is device discovery, not state inspection of playback.

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?

It gives concrete when-to-use guidance: "discover device names — e.g. linked Sonos rooms — before playing or transferring to one," which implicitly routes to the play and transfer siblings. It does not name a when-not condition or state prerequisites such as needing an active Spotify session, so it stops 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.