Self-hostable desktop music player with smart mixes, lyrics, radio, and MCP control. Provides HTTP API endpoints for library management, search, playback control, device sync, and music recommendations.
Resonance MCP server has 15 tools with explicit schemas and descriptions visible in server/src/index.ts. Naming follows verb_noun convention (get_, stream_, search_, download_, register_, sync_, resolve_, send_, play_, start_, health_check). However, descriptions are inconsistent in depth, some are 10-15 chars (health_check: 'Health check endpoint to verify server is running' is adequate at 50 chars), while others lack actionable context for LLM selection. Parameter schemas are present and typed (Zod validation visible), but descriptions for individual parameters are sparse or missing. Output schemas are not documented, LLMs cannot predict response structure. Error handling is minimal; no recovery guidance or categorization. Security: no secrets in params (good), but no audit logging or permission gates visible. Composition is reasonable (single-responsibility tools), but some tools like resolve_playback are complex with many optional parameters that could confuse LLM reasoning.
Download a track by trackId or by videoId with metadata
Get listening history and statistics (capsule overview)
Get status of a download job by ID
Retrieve all tracks, playlists, and devices from the library
Get pairing information including API token, server port, device ID, and QR code
Get current playback state from the desktop player
Health check endpoint to verify server is running
Play a specific track by ID on the desktop player
Output schemas not documented. LLMs cannot predict response structure for any tool, forcing them to guess what fields are returned and breaking downstream tool chaining.
Parameter descriptions missing or minimal. Zod schemas define types but descriptions are absent in the tool registration. LLMs cannot understand what each parameter controls.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 49 | 2026-07-28+ | v2 |
Register a new device or update existing device information
Resolve playback for a track query across devices
Search for tracks by query string
Send a playback control command to the desktop player
Start radio playback based on a seed track with recommendation profile
Stream audio file for a track by ID
Sync track availability and local paths for a device
resolve_playback has 10 parameters with many optional fields (trackId, videoId, title, artists, duration, thumbnail, desktopCanDownload, allowAndroidFallback). This complexity invites LLM confusion about which combination is required. No documentation of parameter dependencies.
No error handling guidance. Tools return success/failure but do not tell LLMs what to do on failure, whether to retry, or what the error means. No recovery paths documented.
Tool descriptions are generic and lack context for LLM selection. E.g., 'Sync track availability and local paths for a device' does not explain WHEN to call this vs resolve_playback, or what 'availability' enum values mean.