Loading ToolBench
Read-only MCP server for Mod Organizer 2 that provides tools for analyzing mod conflicts, looking up mod metadata, and indexing Nexus mod information from local MO2 installations
Server has 5 well-scoped read-only tools with complete input schemas and reasonable descriptions (avg 150 chars). All tools follow verb_noun naming (mo2_*). Schemas include type definitions and parameter descriptions. However, descriptions lack LLM-optimized guidance on WHEN to use each tool vs alternatives, and output schemas are not documented in the tool definitions themselves. Error handling is minimal, no recovery guidance or actionable error messages visible. No tool annotations (readOnlyHint, etc.) despite all being read-only. Parameter descriptions are adequate but could be more prescriptive about constraints and formats.
Scans enabled mods in modlist order and reports paths where multiple mods supply the same virtual path. MO2 mod priority: a mod later in modlist.txt (higher order index) wins over earlier mods for the same virtual path. This scan covers loose files only, not BSA/BA2 contents.
Finds .esp/.esm/.esl plugin files under a specific mod folder up to maxDepth and maxFiles limits.
Resolves a mod folder name from modlist: exact (case-sensitive), then case-insensitive, then unique prefix. Returns mod metadata including enabled status, load order, and meta.ini contents.
Walks modlist and reads only meta.ini per mod folder to extract Nexus-related metadata (mod ID, file ID, version, installation file, game name). This is a disk snapshot, not a live Nexus API call.
Merges loadorder.txt order with plugins.txt active flags to provide a complete plugin load order. Does not read plugin binaries.
Output schemas not documented in tool definitions. LLMs cannot plan downstream calls or extract required fields without knowing response structure (e.g., mo2_asset_conflicts returns AssetConflictsReport with fields like 'conflicts', 'warnings', 'scanned_files', but this is not visible in the tool schema).
No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite all 5 tools being read-only. Agents cannot infer safety properties without explicit hints.
Descriptions lack WHEN-to-use guidance. mo2_mod_lookup and mo2_list_mod_plugins both search mods, but the distinction (lookup by name vs list plugins in a mod) is not explained. LLMs may conflate them.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 46 | 2026-07-28+ | v2 |
mo2_plugins_ordered has empty input schema (no parameters). Description does not explain what data it reads (loadorder.txt, plugins.txt paths) or how it determines the profile/game context.
No error handling guidance visible. If a mod folder is missing or a file cannot be read, tools return warnings in the response, but there is no recovery guidance (e.g., 'Check MO2_MODS_DIR environment variable' or 'Verify modlist.txt is valid').