Loading ToolBench
Proximo Model Context Protocol server for process inspection, DLL export analysis, proxy candidate ranking, and C++ proxy project generation
This server demonstrates solid tool naming and clear descriptions across most tools. Schemas are present and properly typed with Zod validation. However, there are notable gaps in parameter descriptions, missing output schema documentation, and incomplete error handling guidance. The server focuses on a specialized domain (DLL proxy analysis) with technically accurate tool definitions, but lacks some production-grade polish around error recovery and response shaping.
Inspect a running process, analyze all loaded DLLs, extract exports via LIEF, and rank the best DLL proxy candidates (e.g. dinput8.dll, dxgi.dll, version.dll) with score and rationale.
Compile a generated proxy project using CMake and MSVC, producing release or debug binaries.
Generate a complete, compilable C++ / MASM / CMake proxy project with perfect 1:1 export forwarding for any target DLL.
Parse PE headers of any DLL on disk using LIEF and extract all exported functions with names, ordinals, RVAs, and forwarders.
Get detailed information about a specific running process by PID or process name, including memory, architecture, and executable path.
List all loaded DLL modules inside a target process, categorized by proxy suitability (recommended proxy DLLs, local game DLLs, system protected DLLs).
Output schemas not documented for any tool. LLMs cannot predict response structure or plan downstream operations. Tools return JSON text responses but field schemas are invisible to the agent.
Error responses lack recovery guidance. Errors return only status and message (e.g. 'error', '<error message>') but do not tell the LLM what to do next or whether the error is retryable.
generate_proxy_project has complex multi-parameter schema but descriptions lack constraint documentation. The 'selectedFunctionNames' array parameter has minimal guidance on valid function name format or range. The 'customPayloadCode' parameter description lacks safety constraints or injection warnings.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | D | 59 | 2026-07-28+ | v2 |
List running processes on the system with their PID, process name, window title, memory usage, and executable path.
Parameter descriptions are generic and lack actionable format guidance. For example, 'dllFilePath' says 'Absolute or relative file path' but does not specify Windows vs cross-platform path format, character restrictions, or length limits.
No pagination support. list_processes and list_process_modules may return unbounded result sets without limit parameters or cursor-based pagination. Large process lists will blow context windows.
Destructive operations (generate_proxy_project, build_proxy_project) do not offer dry-run or confirmation steps. No confirmation-before-execute pattern implemented.
Tool annotation hints (readOnlyHint, destructiveHint, idempotentHint) are not declared in tool definitions. The protocol supports these hints to guide agent behavior, but they are absent.