Skip to main content
Glama
Sign In
sonos-ts-mcp

sonos-ts-mcp

by Tommertom
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

sonos_play_from_queue

Play a specific track from the Sonos queue by specifying the device and the track's position number in the queue.

Instructions

Start playing from the queue at a specific position.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "deviceId": "<deviceId>",
      "position": "<position>"
    },
    "name": "sonos_play_from_queue"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceIdYesRoom name, UUID, or IP address
positionYesTrack position to start playing from (1-based)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.7

TDQS

B3/5.0
Behavior1/5

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

No annotations provided, and the description does not disclose any behavioral traits beyond the basic action; e.g., whether it continues playback, requires queue non-empty, or affects current state.

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?

Description is a single concise sentence with no wasted words, but could include slight more context without sacrificing brevity.

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?

For a simple tool with 2 parameters and no output schema, the description is adequate but not comprehensive; lacks context to differentiate from sonos_play.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents both parameters. The description adds no additional meaning beyond what the schema provides.

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 uses specific verb 'start playing' and resource 'from the queue at a specific position', clearly distinguishing it from sibling tools like sonos_play (plays from current position) and others.

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?

No guidance on when to use this tool vs alternatives; no mention of prerequisites or context where this tool is appropriate.

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