Skip to main content
Glama
Sign In
roon-mcp

roon-mcp

by bestimmaa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Mute or unmute a Roon zone

mute

Mute or unmute all outputs in a Roon zone. Specify a zone ID or use the default zone.

Instructions

Use this when the user wants to mute or unmute a zone (e.g. "mute", "mute the kitchen", "unmute", "silence the office", "stop the noise"). Mutes (or unmutes) every output in the resolved zone. zoneId is optional and resolves like now_playing. muted: true mutes, muted: false unmutes.

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": {
      "muted": "<muted>"
    },
    "name": "mute"
  }
}

Input Schema

NameRequiredDescriptionDefault
zoneIdNoTarget zone id or output id from list_zones. Omit to use ROON_DEFAULT_ZONE or fall back automatically.
mutedYes`true` to mute, `false` to unmute.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It states that muting affects every output in the zone and explains zoneId resolution. This is sufficient for a simple action, though it lacks detail on side effects or error cases.

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 three sentences, front-loaded with purpose, and every sentence adds necessary context. No unnecessary words.

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 simple action, the description adequately covers usage and behavior. It could mention that no return value is expected, but it's not critical for a mute operation.

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 coverage is 100%, but the description adds value by clarifying zoneId resolves like now_playing and defining the effect of the muted boolean. This goes beyond the schema descriptions.

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 mutes or unmutes a Roon zone, with examples of user queries. It distinguishes from sibling tools like set_volume by focusing on mute/unmute rather than volume control.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly says 'Use this when the user wants to mute or unmute a zone' and provides example utterances. It does not explicitly mention when not to use it or alternatives, but the context is clear enough.

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