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

sonos-ts-mcp

by Tommertom
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

sonos_set_loudness

Enable or disable loudness compensation on Sonos speakers to boost bass and treble at low volumes for improved sound quality.

Instructions

Enable or disable loudness compensation. Loudness boosts bass and treble at low volumes for better sound quality.

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

Input Schema

NameRequiredDescriptionDefault
enabledYesTrue to enable loudness, false to disable
deviceIdYesRoom name, UUID, or IP address

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.7

TDQS

A3.8/5.0
Behavior2/5

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

No annotations provided; description explains the audio effect but does not disclose side effects, permission requirements, or failure modes (e.g., device not found). Basic operational context is missing.

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 words, directly communicates the tool's function and benefit.

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?

Given no output schema and many sibling tools, the description sufficiently explains the tool's effect, though it could mention that the change applies to the specified device and is persistent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 100% coverage with clear parameter descriptions; the description adds value by explaining the purpose of loudness enhancement, which contextualizes the 'enabled' boolean beyond its schema definition.

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?

Description clearly states the tool enables or disables loudness compensation, a specific audio feature, distinguishing it from sibling tools like sonos_set_bass or sonos_set_treble that adjust specific EQ bands.

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?

Description explains that loudness boosts bass and treble at low volumes for better sound quality, implying use during low-volume listening, but lacks explicit when-to-use or when-not-to-use directives compared to alternatives.

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