Loading ToolBench
Generic chat-with-an-agent WordPress plugin built on wordpress/agents-api. Provides custom HTTP tools, tool discovery, and agent integration for WordPress.
openclaWP exposes 3 tools with significant definition gaps. Tool 1 (list-tools) has a complete schema with proper types and descriptions, but Tool 2 (execute-tool) lacks parameter descriptions for the critical 'args' field. Tool 3 (/tools) is inferred from JavaScript and has no visible schema or structured definition in the PHP codebase. Descriptions are present but generic (10-50 chars for /tools). No error handling guidance, no output schemas documented, no tool annotations. The execute-tool pattern is high-risk (WRITE operation) with minimal safeguards visible.
List tools available to the current agent.
Execute one registered ability by slug. The model passes tool (full ability slug) and args (object); the server looks up the ability and dispatches via its execute callback.
List tools available to the current agent with pagination support. Returns tool names, categories, and descriptions filtered by category and allowlist.
/tools has no input schema, no structured output definition, and minimal description (10 chars). Tool is inferred from JavaScript only; no PHP registration visible. Violates pattern:tool requirement for schema documentation.
execute-tool's 'args' parameter lacks description. LLM cannot infer what structure 'args' should contain or what fields are valid. Violates pattern:tool-description (every parameter needs a description).
No output schemas documented for any tool. LLMs cannot plan downstream calls or extract required fields. list-tools and execute-tool return structures that are not formally specified.
execute-tool is a WRITE operation with no error handling guidance, no confirmation step, and no recovery instructions. Agents cannot distinguish retryable from fatal errors. Violates pattern:recovery-guide.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 38 | 2026-07-28+ | v2 |
No tool annotations (readOnlyHint, destructiveHint, idempotentHint) present. execute-tool is marked WRITE but lacks formal annotation. Violates current MCP spec (2026-07-28) tool annotation requirement.