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

sonos-ts-mcp

by Tommertom
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

sonos_subscribe_events

Subscribe to real-time events from a Sonos device service to receive automatic notifications of state changes.

Instructions

Subscribe to real-time events from a Sonos device service to receive automatic notifications of state changes.

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

Input Schema

NameRequiredDescriptionDefault
serviceYesService name to subscribe to
timeoutNoSubscription timeout in seconds (default: 1800 = 30 minutes)
deviceIdYesRoom name, UUID, or IP address

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.7

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries full responsibility for behavioral disclosure. It only states the tool 'subscribes' and 'receives notifications' but omits critical details such as delivery mechanism, side effects (e.g., does it start a background listener?), lifecycle requirements (e.g., session duration), or error conditions (e.g., invalid deviceId).

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, focused sentence that immediately conveys the action and purpose. Every word earns its place with no redundancy or filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity (3 params, no output schema, no annotations), the description is too sparse. It does not explain the subscription response (e.g., subscription ID), the need to manage subscriptions with sibling tools, or how events will be delivered. An agent would lack sufficient context to use the tool correctly in a workflow.

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 already provides 100% coverage with descriptions for each parameter, including an enum for 'service', a default for 'timeout', and a clear description for 'deviceId'. The description adds no additional meaning beyond the high-level purpose, so a 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 uses the active verb 'subscribe' with a clear resource 'real-time events from a Sonos device service' and specifies the outcome 'receive automatic notifications of state changes'. It distinguishes the tool from siblings like 'sonos_unsubscribe_events' by focusing on subscription initiation.

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?

The description provides no guidance on when to use this tool versus alternatives (e.g., when a subscription already exists, or prerequisites like discovering devices). There is no mention of exclusions or alternatives among the numerous sibling tools.

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