Loading ToolBench
Browser Tools MCP for Firefox - Helps with debugging and development tasks
This server has critical structural deficiencies. All 11 tools lack input parameter schemas entirely, they declare empty `{}` objects. Descriptions are present but generic (10-50 chars), providing minimal LLM guidance. No output schemas are documented. The codebase shows Firefox extension architecture (devtools.js, background.js) but no MCP protocol implementation is visible. Tool definitions appear to be inferred from message-passing code rather than formally registered via MCP. This is not a functional MCP server.
Clear all logs (console and network)
Clear all collected console logs
Clear all collected network logs
Retrieve console errors collected from the page
Retrieve console logs collected from the page
Retrieve network error logs
Retrieve successful network request logs
Get the currently selected element data including tag name, id, classes, attributes, computed styles, and outer HTML
All 11 tools declare empty input schemas `{}` with no parameter definitions, types, or constraints. Per HARD SCORING RULE, schema score must be 0 for tools with no input schema.
No output schemas documented for any tool. LLMs cannot plan downstream calls or extract required fields. Baseline: 100% of A+ tools have documented return types.
Tool descriptions are generic and under 50 characters (e.g., 'Stop the element selection mode'). Per HARD SCORING RULE, descriptions under 20 chars score 0-20. Descriptions lack WHEN to use, prerequisites, or state-change implications.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 30 | 2026-07-28+ | v2 |
Start the element selection mode to allow users to select elements on the page
Stop the element selection mode
Capture a screenshot of the currently visible tab
No MCP protocol implementation visible in source. Code shows Firefox extension architecture (devtools.js, background.js, content scripts) with browser.runtime.connect() and browser.tabs.sendMessage(), not MCP transport (HTTP, SSE, or STDIO). Tool definitions appear inferred from message-passing, not formally registered.
Destructive tools (clearConsoleLogs, clearNetworkLogs, clearAllLogs) lack confirmation/dry-run patterns and do not document irreversibility in descriptions. Agents cannot distinguish safe from destructive calls.