Loading ToolBench
CLI npm para instalar, atualizar, verificar e remover o Orquestrador Maestro no usuário atual, com catálogo público deduplicado de skills versionadas.
This MCP server exposes 10 tools for development context management and tool detection. Tool naming is inconsistent: some use verb_noun (compact-worklog, check-dev-gates), others use noun_verb (adapters list, adapters paths). Descriptions are present but generic (avg ~80 chars, below the 194-char baseline). Input schemas are visible and typed, but parameter descriptions are sparse or missing entirely. No output schemas documented. Error handling is absent, no recovery guidance, no categorization. Security concerns: tools like compact-worklog and adapters render perform file I/O without visible permission checks or audit logging. No tool annotations (readOnlyHint, destructiveHint). Overall, definitions are functional but fall short of production quality.
Lists all available tool adapters with their display names, surfaces, and capabilities
Displays configuration paths for a specific adapter by ID
Renders adapter configuration files for a specified adapter (junie, goose, or openhands) into a project directory
Validates the tool adapters manifest for schema compliance and completeness
Validates DEV directory structure and content quality with three modes: structural integrity (default), substantive content validation (--strict), and architectural governance (--architectural)
Flags files, modules, or topics touched across multiple worklog entries (threshold-based) and optionally creates a REPEATED_FAILURES.md file for causal investigation
Compacts worklog by removing oldest entries beyond a specified keep count, archiving them to a separate file
Inconsistent tool naming: 'adapters list', 'adapters paths', 'adapters validate' use noun_verb pattern instead of verb_noun. LLMs struggle to infer intent from non-standard names. Should be 'list_adapters', 'get_adapter_paths', 'validate_adapters'.
No output schemas documented for any tool. LLMs cannot plan downstream calls or extract required fields. E.g., 'adapters list' returns what structure? Array of objects? What fields?
No tool annotations (readOnlyHint, destructiveHint, idempotentHint). Tools like 'compact-worklog' and 'adapters render' perform writes but are not marked destructive. Agents cannot reason about side effects.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 48 | 2026-07-28+ | v2 |
Detects all supported tools on the system and returns their detection states
Detects whether a specified tool is installed, configured, or not detected on the system
Detects a specific tool by ID and returns its detection state
Parameter descriptions are minimal or absent. E.g., 'detectTool' has 'toolId' with description 'Tool identifier to detect', what format? What are valid values? No enum, no examples, no constraints.
No error handling or recovery guidance. If 'adapters render' fails, what should the agent do? Retry? Check permissions? No error categorization or actionable messages.