DouYuSearcher MCP 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
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 |
|---|---|
| get_roomA | |
| search_roomsA | |
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 2 tools
The two tools have clearly distinct purposes: get_room retrieves detailed information for a specific room by ID, while search_rooms finds multiple rooms by keyword with summary information. There is no overlap in functionality or ambiguity about when to use each tool.
Both tools follow a consistent verb_noun naming pattern (get_room, search_rooms) using snake_case. The naming is predictable and follows the same convention throughout the tool set.
With only 2 tools, this server feels underpowered for a comprehensive DouYu search/seamless experience. While the tools cover basic lookup and search, the domain suggests additional operations like filtering by category, trending rooms, or user profiles would be expected for a complete surface.
The tool surface is severely incomplete for a DouYu search domain. There are significant gaps: no ability to browse categories/partitions, get trending/hot rooms, filter search results, or access user/profile information. Agents will hit dead ends when trying to perform common exploration tasks beyond basic ID lookup and keyword search.