Loading ToolBench
A VS Code extension implementing MCP server for WordPress integration
This server has severe definition quality gaps. Tool names lack action verbs (connect, queryDatabase, showConfig, answerConfigQuestion are vague or non-standard). Only 2 of 4 tools have visible input schemas; schemas lack proper JSON Schema structure with type definitions. Descriptions are present but generic (10-50 chars), well below the 50-200 char LLM-optimized baseline. No output schemas documented. No error handling guidance. Tool definitions appear inferred from package.json rather than explicit MCP registration, cannot verify actual schema compliance.
Answer configuration questions about WordPress wp-config.php
Connect to WordPress
Query Database
Show WordPress Configuration
Tool names lack action verbs. 'connect', 'showConfig', 'answerConfigQuestion' are non-standard. Should be 'get_wordpress_config', 'query_database', 'get_config_value'. LLMs cannot infer intent from vague names.
No input schemas visible for 2 of 4 tools (connect, showConfig). Only queryDatabase and answerConfigQuestion show parameter definitions. Cannot verify JSON Schema compliance or type safety.
Descriptions are too short (10-50 chars vs 50-200 char baseline). 'Connect to WordPress', 'Query Database', 'Show WordPress Configuration' lack context for LLM tool selection. No guidance on when to use each tool or what it returns.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 24 | 2026-07-28+ | v2 |
No output schemas documented. LLMs cannot plan downstream calls or extract required fields. What does queryDatabase return? What fields does answerConfigQuestion provide?
Tool definitions inferred from package.json VS Code extension manifest, not explicit MCP server registration. Cannot verify actual MCP protocol compliance or schema validation.