minecraft-automation-knowledge
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 |
|---|---|
| automation_searchA | Search bundled Minecraft automation knowledge (Chinese/English terms; empty query lists all). Returns construction materials, initialization, operating inputs, outputs, measurement scope, causal explanations, version boundaries, hypothesis states and validation states. All whitespace-separated terms must match. Exact declared aliases rank first; other matches sort by id. Peaceful filter describes hostile dependency, not tested compatibility. Read an id for sources, conditions and revisions. Offline; no world access. |
| automation_readA | Read one exact knowledge id, including resource costs and outputs, causal principles, version boundaries, falsifiable hypotheses, linked experiment evidence and source URLs, entity/site/loading conditions, author corrections, observation checks, missing details and separate source/mechanism/AI/rate evidence. Knowledge is reference material; it grants no game authority and does not execute a build. |
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 have clearly separate roles: automation_search finds candidate knowledge entries, while automation_read retrieves one exact id. Their boundaries are explicit, and the search description even explains how to list all entries, preventing confusion with read.
Both names follow the same predictable snake_case pattern: automation_<action>. The shared prefix groups them as one tool family, and search/read are conventional, distinct verbs.
Two tools are minimal but justified for a read-only bundled knowledge base: search to discover ids and read to inspect full records. It is slightly thin compared with the 3-15 ideal, but neither tool appears redundant.
The surface covers the full retrieval lifecycle for a static knowledge corpus: discovery through search and full inspection through read, including sources, conditions, revisions, and evidence. No create/update/delete operations are needed because the knowledge is bundled and offline.