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

sonos-ts-mcp

by Tommertom
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

sonos_restore_snapshot

Restore a saved snapshot to return a Sonos device to its previous state, with optional volume fade-in.

Instructions

Restore a previously saved snapshot to return device to its captured state. Optionally fade in volume.

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

Input Schema

NameRequiredDescriptionDefault
fadeNoFade volume up on restore (default: false)
deviceIdYesRoom name, UUID, or IP address
snapshotYesJSON string of the snapshot to restore

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?

With no annotations provided, the description carries the full burden of disclosure. It mentions the restore action and optional fade, but fails to describe behavioral traits such as whether current playback is interrupted, if the device must be online, or if the operation is irreversible (overwrites current state). This leaves significant gaps for the AI agent.

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?

Two sentences convey the core purpose and a key option. No wasted words, and the most important information (restore snapshot) is front-loaded.

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 (3 parameters, no output schema), the description covers the basics. However, it lacks information about what happens to the current device state, return values (e.g., success confirmation), or error conditions. For a restore operation, more behavioral context would improve completeness.

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 parameter descriptions already provide meaning. The description adds context for the `fade` parameter ('Optionally fade in volume') but does not enhance understanding of `deviceId` or `snapshot` beyond the schema. Baseline score 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 tool restores a previously saved snapshot to return the device to its captured state, with optional fade-in. The verb 'Restore' paired with 'snapshot' distinctly identifies the action, and the sibling tool `sonos_snapshot` for saving makes the counterpart clear.

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 using this tool after a snapshot has been saved, but it does not explicitly state prerequisites (e.g., a snapshot must exist) or provide guidance against alternatives. No when-not-to-use or alternative tool references.

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