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

sonos-ts-mcp

by Tommertom
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

sonos_search_library

Search your Sonos music library by artist, album, track, or genre. Provide device ID, search term, and content type to get matching items.

Instructions

Search the music library by artist, album, track, or genre. Returns matching items.

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>",
      "searchType": "<searchType>",
      "searchTerm": "<searchTerm>"
    },
    "name": "sonos_search_library"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNoNumber of items to return (default: 100)
deviceIdYesRoom name, UUID, or IP address
searchTermYesSearch term
searchTypeYesType of content to search
startIndexNoStarting index for pagination (default: 0)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.7

TDQS

B3.4/5.0
Behavior2/5

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

No annotations provided; description only states 'Returns matching items.' Lacks disclosure of pagination limits (beyond schema), error handling, or potential side effects. Minimal behavioral insight.

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, front-loaded with main action. No unnecessary words. Efficiently conveys core purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 5 parameters, no output schema, and no annotations, description is too brief. Missing details on result set, error behavior, and whether search is local vs online. Incomplete for a search 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% with descriptions. Description adds context by mentioning search categories matching the searchType enum, but provides no additional meaning for other parameters beyond schema. 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?

Description clearly states verb 'Search', resource 'music library', and specifies search categories (artist, album, track, genre). Distinguishes from sibling tools like sonos_search_music_service (external) and sonos_browse_* (browsing).

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 implies use for searching local library, but no explicit guidance on when to use vs browsing or when not to use. Alternatives like browse tools are not 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