Loading ToolBench
An MCP toolkit for modders. Bundles all installed @modwrench/* platform packages into a single combined MCP server with tools for Nexus Mods, mod.io, Thunderstore, and local modding diagnostics.
ModWrench demonstrates solid naming conventions (verb_noun pattern across all 12 tools) and comprehensive parameter schemas with proper enums. However, descriptions vary significantly in quality, some are excellent (mw_activate_platform at 180+ chars with clear context), while others are minimal (mw_deck at 120 chars, workbench_detect_environment with empty input object). Output schemas are not documented in the provided source, forcing LLMs to infer response structure. Error handling guidance is absent, tools return success/failure but lack recovery hints. Tool composition is clean (single responsibility), but several tools lack parameter descriptions for enum values (e.g., logType in workbench_parse_crashlog lists enum values but no description of what each means). Baseline: avg tool description ~150 chars (target 194), avg params ~3.5 (target 4), but 2 tools have undescribed parameters.
Retrieve detailed information about a specific mod on mod.io.
Search for mods on mod.io by name, author, or category.
Activate an additional platform's tool set without restarting the meta-server. Use this when the user adds credentials or asks about a platform that wasn't loaded at boot. After activation, the new tools appear in the catalog and become callable. Returns the activation result (success with toolCount + baseUrl, or failure with reason — usually a missing-credential hint pointing at `modwrench auth login <platform>`).
Returns the ModWrench deck as a ui:// resource built entirely from the current catalog state with four flagship-game themes (Skyrim, Fallout, Lethal Company, Valheim) and no state.
Retrieve detailed information about a specific mod on Nexus Mods.
Search for mods on Nexus Mods by name, author, or category.
Output schemas not documented. LLMs cannot infer response structure for any tool. No field descriptions, types, or pagination guidance visible in source.
workbench_detect_environment has empty input schema (no parameters) but lacks description of what environment data it returns or when to call it.
Enum parameter values lack descriptions. workbench_parse_crashlog lists logType enum (crashlogger-sse, buffout4, bepinex, netscriptframework, auto) but does not explain what each type means or when to use 'auto'.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 54 | 2026-07-28+ | v2 |
Retrieve detailed information about a specific mod on Thunderstore.
Search for mods on Thunderstore by name, author, or category.
Check a list of mod IDs or plugin filenames against LOOT masterlists and community conflict data.
Detect the local modding environment (game installations, mod managers, load order files).
Parse and analyze a crashlog from Crashlogger SSE, Buffout4, BepInEx, or NetScriptFramework.
Parse a load order file (plugins.txt, loadorder.txt, or modlist.txt) from Vortex, MO2, or other mod managers.
No error handling guidance. Tools return success/failure but lack recovery hints (e.g., 'If activation fails, call modwrench auth login <platform>').
mw_deck description is vague ('Returns the ModWrench deck as a ui:// resource'). Does not explain what a 'deck' is, when to call it, or what themes are available.