datapack-check-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DATAPACK_WORKSPACE | No | Spyglass workspace root. Should point to a pack root with pack.mcmeta or a parent directory containing multiple packs. If not set, check_file will search upward from the file for pack.mcmeta; check_project uses the passed root or process cwd. | |
| DATAPACK_CHECK_LOCALE | No | Spyglass diagnostics language. | en |
| DATAPACK_CHECK_FILE_TIMEOUT_MS | No | Timeout in milliseconds for check_file to wait for diagnostics. | 30000 |
| DATAPACK_CHECK_READY_TIMEOUT_MS | No | Timeout in milliseconds to wait for Spyglass to be ready (including first cache download). | 180000 |
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 |
|---|---|
| check_fileA | Run Spyglass (Datapack Helper Plus engine) diagnostics on one Minecraft datapack file (.mcfunction, pack JSON, .mcmeta, .snbt, .mcdoc). Returns path/line/severity/message. |
| check_projectA | Run Spyglass (Datapack Helper Plus engine) on every .mcfunction, pack JSON, .mcmeta, .snbt, and .mcdoc file under a datapack workspace. Pass the pack root (folder with pack.mcmeta) or a parent folder. First run may download the vanilla cache and take a few minutes. |
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 are clearly distinct in scope: one checks a single file, the other checks an entire project workspace. There is no overlap or ambiguity about which tool to use for a given task.
Both tools follow a consistent 'check_' verb-noun pattern, with 'file' and 'project' clarifying the target. The naming is predictable and uniform.
The server has only 2 tools, which is below the typical 3-15 range, but the narrow purpose of checking datapack files is well-served by a file-level and a project-level check. The count is slightly thin but reasonable for the scope.
The domain is linting/diagnostics for datapack files. The server covers both individual file checks and whole-project scans, which are the only two granularities needed. No obvious operations are missing for the stated purpose.