HytaleModding.dev MCP Server
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 |
|---|---|
| search_docsD | Fetch the full content of a Hytale modding documentation page. Provide a doc path (e.g. '/en/docs/official-documentation'). Use search_docs first to find the right page path. |
| get_docA | Fetch the full content of a Hytale modding documentation page. You MUST use the search_docs tool first to get a list of URLs that are compatible with this tool. |
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
Both tools are described as 'Fetch the full content of a Hytale modding documentation page', making them appear to do the same thing. While one is named 'search' and the other 'get', the descriptions do not clearly differentiate their purposes, leaving agents confused about which to use.
Both tool names follow a verb_noun pattern (search_docs, get_doc), but one uses the plural 'docs' and the other singular 'doc', a minor inconsistency. The verbs 'search' and 'get' are distinct and reasonably clear.
With only 2 tools, the server feels minimal. For a documentation server, a search and fetch pair is plausible, but the count is at the lower end of what is reasonable for a coherent toolset.
The server appears to cover searching and fetching documentation pages, but the unclear boundary between the tools leaves a gap in understanding how to discover pages without already knowing a path. A clearer search step or listing mechanism would make the surface more complete.