掌锤公开查询 MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ZHANGCHUI_API_BASE | No | API base URL. Only accepts credential-free HTTPS addresses. | https://40kdata.online/api/v1/public-query |
| ZHANGCHUI_TIMEOUT_SECONDS | No | Request timeout in seconds. Must be greater than 0 and no more than 60. | |
| ZHANGCHUI_MIN_INTERVAL_SECONDS | No | Minimum interval in seconds between HTTP requests. Must be between 0 and 60. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_reportsB | 找已上线报告；日期按报告统计窗口筛选。每页20条，先从结果取得report_id和release_id。 |
| get_reportB | 读取指定报告和预先计算的阵营统计，原始胜率与估计胜率分别保留；用release_id固定版本。 |
| get_matchupsB | 按所选报告的日期、规则、地区和赛制查询已存对阵；不是跨期MFM汇总，每页20条。 |
| list_rostersA | 列出该报告允许公开的军表摘要，每页20条；从结果取得case_id，再调用get_roster。 |
| get_rosterB | 读取该报告关联的一份公开军表；保留原文、中译、来源及未确认状态，不把未知点数补为0。 |
| get_data_notesA | 读取报告统计口径、原始来源和日期依据；分析或跨报告比较前先查这里。 |
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 6 tools
The list/get pairs for reports and rosters are clearly distinct, and get_matchups targets a separate data type. The only mild overlap is between get_report and get_data_notes, since both concern report-level information, but the descriptions clarify statistics versus methodology.
All tool names follow a consistent verb_noun pattern: list_reports, get_report, get_matchups, list_rosters, get_roster, get_data_notes. The convention is predictable and easy for an agent to follow.
Six tools is well-scoped for a read-only public query server covering reports, matchups, rosters, and methodology notes. Each tool has a clear place in the workflow.
The surface covers the core read-only lifecycle: list reports, read report stats, query matchups, list and read public rosters, and consult data notes. Minor gaps may exist around more granular filtering or faction-level queries, but agents can work around them.