MCP server for Opera DevTools providing browser automation, debugging, and performance analysis tools
Three tools with minimal descriptions (10-20 chars each) and empty input schemas. 'screenshot' and 'navigate' lack parameter descriptions entirely. 'evaluate' has a single param with minimal guidance. No output schemas documented. Tool names are action verbs (positive), but descriptions are far below the 50-200 char baseline for LLM-optimized tools. No error handling guidance, no pagination, no structured output documentation. This server falls well below production quality.
Evaluates a JavaScript script
Loads a URL
Takes a screenshot
screenshot tool has empty input schema ({}) and 10-char description ('Takes a screenshot').
navigate tool description ('Loads a URL') is 10 chars, below 20-char minimum. Parameter 'url' has description but tool-level context is insufficient for LLM selection.
No output schemas documented for any tool. LLMs cannot plan downstream calls or extract structured data. Baseline: 100% of A+ tools have documented return types.
No error handling guidance. Tools do not explain what to do on failure (retry? ask user? fatal?). Per pattern:recovery-guide, errors must tell the LLM what to do next.
Inferred effective spec: 2025-06-18+.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 41 | 2025-06-18+ | v2 |
evaluate tool accepts arbitrary JavaScript with no validation, sanitization, or scope documentation. Agents could inject malicious code. Missing security boundary documentation.