Loading ToolBench
MCP server for WebWeaver Nexus — waitlist form, product overview, and contact info
Descriptions exist but are brief (10-20 chars for tool names, longer for full descriptions). No parameter descriptions exist because no parameters are defined. Tools lack error handling guidance, output schema documentation, and composition patterns. The server is essentially a static information provider with no real agent integration patterns.
Returns contact methods and links for WebWeaver Nexus.
Returns a short description of what WebWeaver Nexus does.
Opens the WebWeaver Nexus contact form. Use it to secure a priority booking for the "AI-Ready" Discovery & Audit, or enquire about a particular service.
All tools have empty input schemas ({}). This prevents LLMs from understanding what parameters are accepted and makes tools non-composable.
No output schemas documented. LLMs cannot plan downstream tool calls or extract structured data. Responses are plain text, not typed objects with predictable fields.
No error handling or recovery guidance. If a tool fails, the LLM has no actionable next step. No distinction between retryable vs fatal errors.
join_waitlist has no parameters but description implies user input (filling out a form). Should accept optional parameters like email, name, or service_inquiry to pre-populate the form or validate user intent.
Inferred effective spec: 2026-07-28+.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 47 | 2026-07-28+ | v2 |
Tool descriptions lack WHEN-to-use context. LLMs cannot distinguish between get_product_overview and get_contact_info without explicit guidance on which to call first or when each is appropriate.