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

sonos-ts-mcp

by Tommertom
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

sonos_remove_from_queue

Remove a specific track from a Sonos queue by providing the device and the track's position number.

Instructions

Remove a track from the queue at the specified 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_remove_from_queue"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.7

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description bears the full burden. It discloses the core removal behavior but does not discuss side effects, error conditions, or implications for playback. The behavior is simple, so a score of 3 is acceptable.

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, front-loaded sentence that efficiently conveys the tool's purpose. No unnecessary words or complexity.

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 and the lack of annotations or output schema, the description is minimally adequate. It covers the primary action but omits details on error handling, prerequisites, and the exact effect on the queue state.

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 coverage is 100%, so the baseline is 3. The description adds no extra meaning beyond what the schema provides for deviceId and position. It does not explain the 1-based indexing or context for deviceId.

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 tool removes a track from the queue at a specified position, using a specific verb and resource. It distinguishes itself from sibling tools like add_to_queue, clear_queue, and play_from_queue.

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 usage guidelines are provided. The description does not indicate when to use this tool over alternatives, nor does it give context on prerequisites or typical scenarios.

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