Loading ToolBench
MCP server for Project Zomboid mod development: Java API docs, vanilla Lua/script lookup, and mod project tooling.
Server has 20 well-named tools with consistent verb_noun patterns (javadoc_*, apidocs_*, source_*, lua_*, scripts_*, mod_*). All tools have descriptions (avg ~80 chars, within baseline 34-392). Input schemas are present and typed for all tools. However, descriptions are terse and lack WHEN/WHY guidance; parameter descriptions are minimal; output schemas are undocumented; error handling is absent from definitions. mod_scaffold is destructive (WRITE risk) but has no confirmation pattern or dry-run option. No tool annotations (readOnlyHint/destructiveHint). Composition is sound, tools chain well (e.g., search → details → hierarchy). Naming is clear and action-oriented.
List all pages in the PZ-API-Docs repository.
Parse and list all parameter/attribute entries from a PZ-API-Docs page.
Get the section outline (headings) of a PZ-API-Docs page.
Extract a specific section from a PZ-API-Docs page.
Read and render a PZ-API-Docs page as markdown.
Search PZ-API-Docs pages by title or slug.
Search the Project Zomboid Javadoc for members (methods, fields) by name.
Search the Project Zomboid Javadoc for types (classes, interfaces, enums) by name.
Output schemas undocumented. No tool returns a documented response structure. LLMs cannot plan downstream calls or extract fields reliably.
Destructive tool (mod_scaffold, WRITE risk) lacks confirmation pattern or dry-run option. Agents can overwrite existing mod projects without safeguard.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint). Clients cannot distinguish safe reads from destructive writes at a glance.
Descriptions lack WHEN/WHY context. E.g., 'Search the Project Zomboid Javadoc for types' does not explain when to use javadoc_search_types vs javadoc_type_details. LLMs cannot disambiguate.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 56 | 2026-07-28+ | v2 |
Get detailed documentation for a specific Java type from the Javadoc, including inheritance, members, and descriptions.
Get the type hierarchy (supertypes and subtypes) for a Java class.
Find classes that implement a given interface.
List all vanilla Project Zomboid Lua events.
List all global Lua functions defined in the vanilla game.
Lint a mod's Lua code for unknown methods, globals, and events.
Create a new Project Zomboid mod project with boilerplate files.
List all script blocks (item, recipe, vehicle, etc.) from the vanilla game.
Search script blocks by type and name.
Find Java classes in the decompiled source by name.
Find method or field declarations in the decompiled source by name.
Read the source code of a Java class, optionally a line range.
No error handling guidance in tool definitions. If a search returns no results or a file is not found, LLMs have no recovery path documented.