Loading ToolBench
Enhanced IDA Pro MCP Server - multi-instance broker + bulk export for AI analysis
Server has 12 tools with basic schemas and descriptions, but significant gaps limit production readiness. Tool names follow verb_noun convention (idalib_open, idalib_close, list_instances), which is good. However, descriptions are inconsistent in depth, some are 10-15 chars (idalib_unbind: 'Unbind the active idalib context from any session' is adequate but terse), while others lack context on when to use them. Parameter descriptions exist but are minimal (e.g., 'Session ID to close' for idalib_close lacks guidance on consequences). No output schemas are documented, callers cannot predict response structure. Error handling is absent from visible code; no recovery guidance. Security concerns: session_id is passed as a parameter, risking exposure in logs. Tool composition shows state management (idalib_switch, idalib_bind) that could be clearer about side effects.
Close an IDA session and remove all context bindings targeting it.
Get the session bound to the active idalib context.
Check the health status of the active idalib context's session.
List sessions with context-binding and active-database metadata.
Open a binary and bind it to the active idalib context policy.
Save the active idalib context's database to disk.
Bind the active idalib context to a session and activate it.
No output schemas documented. Callers cannot predict response structure, forcing LLMs to guess field names and types. This breaks tool chaining and wastes tokens on exploratory calls.
Descriptions lack context on when to use each tool and what happens as a side effect. E.g., idalib_switch says 'Bind the active idalib context to a session and activate it' but does not explain what 'activate' means or whether prior bindings are cleared.
session_id and host/port parameters are passed as strings with no validation hints. LLMs cannot infer format constraints (e.g., is session_id a UUID, alphanumeric, or arbitrary?). No enum or pattern guidance.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 50 | 2025-06-18+ | v2 |
Unbind the active idalib context from any session.
Warm up the active idalib context's session for analysis.
List all connected IDA instances available through the broker.
Open a binary file in an IDA instance.
Select an active IDA instance by host and port.
No error handling or recovery guidance visible. If idalib_close fails (e.g., session not found), there is no indication of what the LLM should do next or how to diagnose the problem.
Tool composition shows state management (idalib_switch, idalib_unbind, idalib_current) but lacks clarity on idempotency. Calling idalib_switch twice with the same session_id should be safe, but this is not documented.