DayZ API 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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_functionB | Search for functions in DayZ vanilla scripts by semantic description |
| get_function_detailsA | Get detailed information about a specific function including signature, parameters, and usage |
| validate_codeB | Validate Enforce Script code against Iron Rules and check for common mistakes |
| find_usage_examplesA | Find real usage examples of a function from vanilla DayZ scripts |
| get_class_hierarchyB | Get class inheritance hierarchy and modded extensions |
| find_vanilla_alternativeC | Check if custom code has vanilla DayZ function alternative |
| parse_scriptB | Parse Enforce Script code and extract classes, methods, enums |
| find_callersA | Find who calls a specific method in vanilla DayZ scripts (reverse call graph) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| DayZ Classes | List of all indexed DayZ classes |
| RPC Setup Pattern | Standard RPC setup pattern for DayZ mods |
| Singleton Pattern | Proper singleton implementation for DayZ |
| Iron Rules of Enforce Script | Critical rules that must be followed in Enforce Script |
| Vanilla Source File | Read content of a vanilla DayZ script file. Use absolute path like P:/scripts/4_world/entities/dayzplayerimplement.c |
TDQS
Scored across 8 tools
Each tool has a distinct and clearly defined purpose, such as finding callers, usage examples, or validating code, with minimal overlap in functionality.
All tool names follow a consistent verb_noun pattern in snake_case, making them predictable and easy to understand.
With 8 tools, the set is well-scoped for the domain of DayZ scripting API exploration, covering essential operations without unnecessary bloat.
The tool set covers a comprehensive range of actions including searching, parsing, validating, and retrieving details about functions and classes, with no obvious gaps for the intended purpose.