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

sonos-ts-mcp

by Tommertom
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

sonos_unsubscribe_all

Unsubscribe from all active event subscriptions for a Sonos device by providing its room name, UUID, or IP address.

Instructions

Unsubscribe from all active event subscriptions for a specific device.

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

Input Schema

NameRequiredDescriptionDefault
deviceIdYesRoom name, UUID, or IP address

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.7

TDQS

A3.5/5.0
Behavior2/5

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

The description discloses that the tool performs a mutation (unsubscribing) but no annotations are present. It lacks details on required permissions, reversibility, side effects on ongoing events, or whether it is idempotent. For a tool with zero annotations, the description should provide more behavioral context.

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, direct sentence that immediately conveys the action and scope. No extraneous words or unnecessary details.

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 (one parameter, no output schema, no annotations), the description covers the basic purpose and scope. However, it lacks any guidance on prerequisites, side effects, or usage context, leaving gaps that could be filled for a more complete picture.

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?

The input schema covers the single parameter (deviceId) with a clear description ('Room name, UUID, or IP address'). The description adds minimal value by specifying 'specific device' but does not enhance understanding beyond the schema. With 100% schema coverage, baseline score of 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 (unsubscribe) and the resource (all active event subscriptions for a specific device). It distinguishes from sibling tools like sonos_unsubscribe_events and sonos_list_subscriptions by specifying 'all' and 'for a specific device'.

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 unsubscribing from all subscriptions on a device, but does not explicitly state when to use this tool versus sonos_unsubscribe_events (which presumably unsubscribes from a single subscription) or other alternatives. No when-not-to-use criteria are provided.

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