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

sonos-ts-mcp

by Tommertom
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

sonos_set_treble

Adjust treble EQ on Sonos speakers from -10 (reduced) to +10 (enhanced) to fine-tune sound balance.

Instructions

Set treble EQ level. Range: -10 (reduced treble) to +10 (enhanced treble).

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>",
      "treble": "<treble>"
    },
    "name": "sonos_set_treble"
  }
}

Input Schema

NameRequiredDescriptionDefault
trebleYesTreble level (-10 to 10)
deviceIdYesRoom name, UUID, or IP address

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.7

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the full burden. It discloses the range and effect (reduced/enhanced treble), which is essential. However, it does not mention other behavioral traits like whether the change is instantaneous, if it persists across sessions, or if it affects other EQ settings. It is minimally adequate.

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 sentence that immediately states the action and range. There is no extraneous text, and it is front-loaded with the core purpose.

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?

For a simple setter with 2 parameters and no output schema or annotations, the description covers the essential information. It could optionally mention that it sets treble for a specific device, but the deviceId parameter makes that clear. It is fairly complete given the simplicity of the tool.

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 both parameters are already described in the schema. The description adds the range for treble but does not provide additional semantics beyond what the schema already states (e.g., for deviceId, the schema says 'Room name, UUID, or IP address'). Baseline 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 verb 'Set' and the resource 'treble EQ level', including the range. It distinguishes from sibling tools like sonos_set_bass or sonos_set_loudness by specifying the exact EQ parameter.

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?

No guidance is provided on when to use this tool vs alternatives. There are many EQ-related siblings (bass, loudness, night mode, dialog mode), but the description does not help the agent decide which to use. No exclusions or prerequisites are mentioned.

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