DDNet 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_ddnet_game_statusB | 获取ddnet进程状态 |
| check_bindC | 检查按键是否被占用 |
| add_bindD | 增加bind |
| delete_bindD | 删除bind |
| get_friend_listD | 获取好友列表 |
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 5 tools
All tools have distinct purposes: three bind operations (add, check, delete), one game status, and one friend list. No overlap.
All tools follow consistent snake_case verb_noun pattern (e.g., add_bind, get_ddnet_game_status), making predictions easy.
5 tools is appropriate for this domain, covering both bind management and game status without being too few or too many.
Covers core bind lifecycle (add, check, delete) but misses update/edit. Status and friend list are present, so only a minor gap.