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

sonos-ts-mcp

by Tommertom
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

sonos_previous

Skip to the previous track on your Sonos device, or restart the current track if it has been playing for more than a few seconds.

Instructions

Skip to previous track or restart current track if played more than a few seconds.

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>"
    },
    "name": "sonos_previous"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceIdYesRoom name, UUID, or IP address

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.7

TDQS

A4/5.0
Behavior4/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 discloses the dual behavior (previous vs restart) which adds value beyond the name and schema.

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, well-structured sentence that efficiently communicates the tool's behavior without any superfluous words.

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 simple tool with one parameter and no output schema, the description adequately covers the behavioral nuances (skip vs restart) making it sufficiently complete.

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% for the single parameter (deviceId). The description does not add any additional semantics beyond what the schema already provides, so baseline 3 is appropriate.

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 action ('skip to previous track or restart current track') and specifies a condition ('if played more than a few seconds'), making it distinct from siblings like sonos_next.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for track navigation but does not provide explicit guidance on when to use this tool versus alternatives like sonos_next or sonos_play.

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