Loading ToolBench
JavaScript reverse engineering and debugging via Chrome DevTools. Built on Patchright anti-detection engine — passes mainstream browser fingerprint checks (Zhihu, Google, etc.) out of the box.
Critical failure: Tool definitions are inferred from a test file (tests/final-tools-list.mjs) rather than visible in actual source code. No explicit tool registration, schemas, or descriptions are visible in the provided source excerpt. The DevToolsConnectionAdapter.ts shows infrastructure but no tool definitions. Cannot verify parameter types, descriptions, or output schemas.
Tool definitions inferred from test file, not visible in source code. No explicit tool registration with schemas or descriptions found in provided source.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 31 | <=2025-11-25 | v2 |
No parameter descriptions visible. Cannot verify that each parameter has a description explaining what it controls.
No input schemas visible. Cannot verify JSON Schema with types, enums, or constraints for any tool parameters.
No output schemas documented. Cannot verify that tools return structured objects with typed fields or pagination support.
Generic/ambiguous tool names: 'step', 'risk_panel', 'pause_or_resume' lack clarity on what action they perform. LLMs cannot infer intent from these names alone.