Loading ToolBench
Desktop app to inspect Java mod jars and estimate Java and game versions.
This server has 16 tools with basic descriptions but critical gaps in schema completeness and parameter documentation. Most tools lack detailed input parameter descriptions, parameters are defined with type and description fields, but descriptions are often generic (e.g., 'Migration workspace object' without explaining structure). No output schemas are documented. Tool names follow verb_noun convention (good), but descriptions are inconsistent in length and detail. Error handling is absent, no recovery guidance, no categorization of errors, no actionable messages. The server is Electron-based (STDIO transport), which caps protocol readiness at 50 and limits remote accessibility.
Get application name and version information
Apply automatic patches to a migration workspace
Convert an artifact to a target loader/version configuration
Create a migration workspace based on inspection results and migration plan
Inspect a mod file to extract metadata, loader type, Java version, and game version
Get available migration options including loaders, game versions, and Java versions
Open a file or folder path in the system file explorer
No output schemas documented for any tool. LLMs cannot predict response structure, forcing them to guess at field names and types for downstream tool chaining.
Parameter descriptions are generic and lack actionable detail. 'Migration workspace object' and 'Target configuration' do not explain structure, required fields, or format. LLMs cannot validate inputs without explicit constraints.
No error handling or recovery guidance. Tools like run-workspace-script (IRREVERSIBLE) and run-workspace-builds (WRITE) lack confirmation steps, dry-run modes, or error categorization. Agents cannot safely retry or recover from failures.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 42 | 2026-07-28+ | v2 |
Open a dialog to select a mod file (jar, zip, class, litemod, etc.)
Open a dialog to select a mod folder
Plan a migration from current mod configuration to a target configuration
Prepare decompilation for a migration workspace
Run a benchmark on mods in a folder with a target configuration
Run a single stage build within a migration workspace
Run all workspace builds for a migration workspace
Execute a PowerShell script within a workspace
Handle window actions including minimize, toggle-maximize, close, and get-state
STDIO transport only. Server is not remotely accessible and cannot be used by hosted MCP clients. Limits deployment to local Electron app only.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint). Clients cannot distinguish safe read-only tools from destructive ones without parsing descriptions. Risk classification is implicit, not explicit.