Loading ToolBench
MCP server for manufacturing: welding, paint, assembly, lean, production planning. Factory optimization.
All 12 tools share identical, severely deficient schemas and descriptions. Each tool accepts only a single 'input' parameter (type: string, description: 'Input data (JSON)') with no structured schema, no parameter validation, and no guidance on expected JSON structure. Descriptions are 15-30 characters, below the 20-char hard floor, providing no context for when/why to use each tool. No output schemas documented. No error handling guidance. Tools are thin pass-through wrappers to an external Bankr API with hardcoded wallet and endpoint. This violates 40+ patterns from the Arcade rubric.
5S assessment tool
8D problem solving report
Assembly process designer
Production capacity calculator
CKD/SKD assembly cost calculator
Kaizen event planner
Production line layout optimizer
All tool descriptions are under 20 characters (e.g., 'Welding process designer' = 24 chars but lacks context for when/why to use). Descriptions must explain WHAT the tool does, WHEN to use it, and any prerequisites.
All tools accept a single 'input' parameter of type 'string' with description 'Input data (JSON)'. No structured schema, no enum constraints, no format validation, no min/max bounds. LLMs cannot infer what JSON structure is expected.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 24 | 2026-07-28+ | v2 |
Localization content calculator
Paint process designer
Value stream mapper
Welding process designer
Workstation designer
No output schemas documented. Tools return raw JSON from external Bankr API wrapped in generic text response. LLMs cannot plan downstream calls or extract structured data. No pagination, no result limits, no field documentation.
Error handling is minimal: catch-all try/catch returns {status: 'error', error: e.message}. No recovery guidance, no error classification (retryable vs fatal), no actionable next steps for LLM. Violates recovery-guide pattern.
Hardcoded wallet address (0xc521cc3eae2a6a3cde11c8bde0b46006d6847360) and Bankr API endpoint in source code. No environment variable injection, no secret management. Credentials exposed in repository.