Skip to main content
Glama
Sign In
Sonora MCP

Sonora MCP

by encodi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List devices

list_devices
Read-only

Retrieve available Spotify Connect devices and their IDs to target playback or transfer audio to a phone, computer, or speaker.

Instructions

List the user's available Spotify Connect devices (phone, computer, speaker). Returns the id to pass as device_id to play or transfer_playback. A device only appears while its Spotify app is open.

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.1.0-dev

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds a real operational caveat that a device appears only while its Spotify app is open, which explains empty results and staleness. It also identifies the key returned field (`id`), valuable given there is no output schema, though it does not describe the other returned fields or ordering.

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?

Three short sentences, each carrying distinct information: what is listed, what to do with the result, and the availability constraint. The purpose is front-loaded and no sentence is redundant.

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 zero-parameter read tool with openWorldHint and no output schema, the description covers purpose, the actionable return field, and the visibility constraint. Only the shape of the remaining device attributes is left implicit, which is a minor gap given the tool's simplicity.

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 nothing for the description to disambiguate and the baseline of 4 applies. The mention of `device_id` refers to an argument of other tools, not this one, and is correctly framed as such.

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 ("List the user's available Spotify Connect devices") and parenthetically enumerates concrete device types, so the agent knows exactly what comes back. It is unmistakably distinct from now_playing and search without needing either schema.

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?

Explains the downstream purpose precisely: the returned `id` is what to pass as `device_id` to `play` or `transfer_playback`, which tells the agent when to call this first. It stops short of naming a sibling as an alternative or stating when not to call it, so it is clear but not fully exclusive.

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

Deploy Server

Other Tools