神岛数据统计 MCP 服务器
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| getUserProfileByUserIdB | 使用用户ID获取神岛平台用户的个人资料数据 |
| getMapInfoByUserIdC | 使用地图ID获取神岛平台地图详情 |
| getMapCommentListByUserIdC | 使用地图ID获取神岛平台地图评论列表 |
| getMapReleaseInfoByUserIdC | 使用地图ID获取神岛平台地图发布信息 |
| getMapListByUserIdB | 使用用户ID获取神岛平台地图列表 |
| getModelListByUserIdB | 使用用户ID获取神岛平台模型列表 |
| getFavoriteListByUserIdB | 使用用户ID获取神岛平台收藏列表 |
| getRecentlyPlayListByUserIdA | 使用用户ID获取神岛平台最近游玩列表 |
| getFollowerListByUserIdA | 使用用户ID获取神岛平台粉丝列表 |
| getFriendListByUserIdA | 使用用户ID获取神岛平台好友列表 |
| getFollowingListByUserIdA | 使用用户ID获取神岛平台关注列表 |
| getMapListByKeywordC | 使用关键字搜索获取神岛平台地图/模型列表 |
| getMapStatListC | 获取神岛平台用户地图统计列表，需Token和用户请求头 |
| getMapPlayerStatListC | 获取神岛平台用户地图玩家统计，需Token和用户请求头和地图ID |
| getMapPlayerRetentionC | 获取神岛平台用户地图玩家留存，需Token和用户请求头和地图ID |
| getMapPlayerBehaviorC | 获取神岛平台用户地图玩家行为，需Token和用户请求头和地图ID |
| getCommentListC | 获取神岛平台用户的评论列表，需要Token和用户请求头 |
| getLikeListB | 获取神岛平台用户的点赞列表，需要Token和用户请求头 |
| getSystemMsgListA | 获取神岛平台用户的系统消息列表，需要Token和用户请求头 |
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 19 tools
Each tool targets a distinct data entity (map info, comments, lists, stats), but getMapInfoByUserId and getMapReleaseInfoByUserId could be confused, as could getMapCommentListByUserId and getCommentList. Overall, scope is clear.
All tools use the get prefix and camelCase, generally following get<Resource>By<Parameter>. Some tools like getMapStatList and getMapPlayerStatList deviate from the By pattern, but the naming is still predictable.
19 tools is within the 16-25 heavy range; for a data retrieval server this is reasonable, though it could potentially be streamlined.
Covers user profiles, social lists, map/model data, statistics, and user interactions. Missing model details and leaderboard data, but core statistics workflows are covered.