Loading ToolBench
Test webhook endpoints -- send POST/PUT/PATCH/DELETE with custom headers and payloads. Measure latency and TLS.
Single tool 'api_test_webhook' has a well-structured schema with all required parameters typed and described. Description is comprehensive (300+ chars) and includes use cases and anti-patterns (what NOT to use it for). Schema includes proper constraints (timeout max: 30s, method enum). However, output schema is documented only in prose within the description rather than as a formal JSON Schema object, and tool lacks explicit error handling guidance for common failure modes (timeout, TLS errors, invalid URL).
Use this when you need to test a webhook endpoint by sending a request with custom headers, body, and method. Returns full response data in JSON. Returns: 1. statusCode 2. responseBody (parsed JSON or text) 3. responseHeaders (key-value map) 4. latency in ms 5. tlsInfo (protocol, cipher) 6. method used 7. requestSize and responseSize in bytes. Example output: {"url":"https://hooks.example.com/callback","method":"POST","statusCode":200,"responseBody":{"received":true},"latency":142,"tlsInfo":{"protocol":"TLSv1.3","cipher":"AES-256-GCM"},"requestSize":256,"responseSize":48} Use this FOR testing webhook integrations, debugging API callbacks, validating endpoint availability, and measuring webhook response times. Do NOT use for web scraping -- use web_scrape_to_markdown instead. Do NOT use for screenshot capture -- use capture_screenshot instead. Do NOT use for HTTP header security audit -- use network_analyze_headers instead.
Output schema not formalized in JSON Schema format. Response structure documented only in prose description ('Returns: 1. statusCode 2. responseBody...'). LLMs cannot reliably parse prose schemas for downstream tool chaining.
No error handling guidance. Tool description lacks recovery hints for common failures: timeout, TLS certificate errors, invalid URL format, connection refused. LLM cannot determine retry strategy or fallback actions.
Missing parameter constraints on 'headers' and 'body' objects. No guidance on max size, forbidden header names (e.g., Authorization), or JSON depth limits. LLM may pass oversized or malformed payloads.
Tool description includes anti-patterns (what NOT to use for) but lacks positive guidance on WHEN to use it. No mention of prerequisites (e.g., webhook must be publicly accessible, HTTPS required) or typical use cases beyond the generic 'testing webhook integrations'.
Inferred effective spec: 2025-06-18+.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 67 | 2025-06-18+ | v2 |