MCP QQ Music Test Server
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_musicB | Search for music tracks Args: keyword: Search keyword or phrase page: Page number for pagination (default: 1) num: Maximum number of results to return (default: 20) Returns: List of music tracks matching the search criteria |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'search_music' has a clear, distinct purpose that cannot be confused with any other tool in this server.
The naming pattern cannot be evaluated for consistency across multiple tools, but the single tool name 'search_music' follows a clear verb_noun convention that is appropriate and readable. There are no inconsistencies to assess.
A single tool is too few for a music server's apparent scope, which typically involves operations like playing, pausing, getting recommendations, managing playlists, or accessing user libraries. This minimal set severely limits functionality and suggests an incomplete implementation.
The server is severely incomplete for a music domain, offering only search functionality without any way to play, queue, control playback, access user data, or manage music collections. This creates significant gaps that will cause agent failures in typical music-related workflows.