lxmusic
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_musicD | – |
| search_albumD | – |
| play_musicD | – |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool targets a distinct resource or action: search_music finds tracks, search_album finds albums, and play_music plays a selected item. Names clearly differentiate the purposes, so an agent can easily select the right tool.
All tool names follow a consistent verb_noun pattern: search_music, search_album, play_music. No mixed conventions, making the API predictable.
With 3 tools, the server is minimal but well-scoped for its apparent purpose of music search and playback. It sits at the lower end of the ideal range but each tool earns its place.
The core workflow is covered: search for music or albums, then play. Minor gaps like pause/stop or playlist management are absent, but these may be outside the intended scope.