esq-builder-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ESQ_VALIDATOR_PATH | No | 设定后 esq_validate_package 改走官方校验器 CLI（对账/仲裁通道）；默认内置校验器，不需要此变量 |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| esq_build_packageC | 校验并构建 ESQ 1.0 题库包 ZIP。 |
| esq_validate_packageB | 校验 ESQ 包（默认内置校验器, 与刷题机官方 esq.py 同规则）。 |
| esq_upload_and_publishA | 上传 ESQ 包到刷题机后端并（可选）发布。上传前先 esq_validate_package。 |
| esq_parse_wordlistC | 解析 kajweb/dict 高频词表 JSONL（wordRank=真题词频排序）。 |
| esq_hot_wordsB | 真题 passage 文本 → 热点词频统计（去停用词, [a-zA-Z][a-zA-Z'-]{3,}）。 |
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
esq_build_package and esq_validate_package overlap slightly since build also validates, but the descriptions clarify that build produces a ZIP while validate is a standalone check used as a pre-upload step. esq_parse_wordlist and esq_hot_words both deal with word frequency but target clearly different inputs (wordlist JSONL vs passage text).
All tools share the esq_ prefix and mostly follow a verb_noun pattern (build_package, validate_package, upload_and_publish, parse_wordlist). esq_hot_words breaks the pattern as a bare noun phrase, a minor deviation.
Five tools is well-scoped for a package builder/publisher, and each tool earns its place in the build-validate-upload pipeline plus two auxiliary analysis utilities.
The core lifecycle (build, validate, upload/publish) is covered, and the word-frequency helpers round out the domain. Minor gaps exist for listing/managing previously built packages, but the primary workflow has no dead ends.