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

sonos-ts-mcp

by Tommertom
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

sonos_set_night_mode

Set night mode on Sonos home theater devices to reduce loud sounds and enhance quiet sounds for late-night viewing.

Instructions

Set night mode for home theater devices. Reduces loud sounds and enhances quiet sounds for late-night viewing.

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

Input Schema

NameRequiredDescriptionDefault
enabledYesTrue to enable night mode, false to disable
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?

Describes the behavioral effect of enabling night mode (reduces loud sounds, enhances quiet sounds). No annotations exist, so the description carries the full burden; it adequately discloses the tool's impact.

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, no unnecessary information. Front-loaded with the action and resource, then explains the effect efficiently.

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?

Completeness is good for a simple boolean toggle. The description explains what night mode does, and the schema covers parameters fully. Could mention device compatibility but not essential.

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%, with both parameters well-described. The tool description adds no additional meaning beyond the schema, so 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?

Clearly states the action (set) and resource (night mode), with a specific description of its effect (reduces loud sounds, enhances quiet sounds). Distinguishes from sibling tools like sonos_set_mute or sonos_set_loudness.

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?

Implied usage for late-night viewing, but lacks explicit when-to-use, when-not-to-use, or alternatives. The context from sibling tools provides some differentiation, but the description itself offers no usage guidance.

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