Loading ToolBench
This server exhibits severe definition quality issues across all dimensions. Tool names lack action verbs (route_mcp_request, handle_mcp_request are generic; list_product_names_mock is confusing). Descriptions are present but vague and lack actionable guidance. Input schemas are partially defined but many parameters lack type information or descriptions. The 'request' tool exposes implementation details (HTTP method, endpoint path) that should be abstracted. No output schemas are documented. Error handling is minimal. The mock tool naming convention is non-standard. Overall, this server would not pass code review for production use.
Generates a response using OpenAI API with optional context. Takes a prompt and context messages and returns generated content.
Handles MCP requests via HTTP POST endpoint. Validates Wildberries API key configuration and routes requests to the MCP router.
Health check endpoint that returns the status of the server and application name.
Executes MOCK list_product_names with API key and parameters. Returns a list of product names from mocked data.
Executes a request to Wildberries API with the appropriate token for the specified section. Handles authorization headers and error handling.
Processes MCP-requests and routes them to corresponding services. Validates API key configuration for different resource types and returns success or error responses.
Generic tool names lack action verbs. 'route_mcp_request' and 'handle_mcp_request' do not convey what action occurs; 'request' is dangerously ambiguous. LLMs cannot infer intent from these names alone.
No output schemas documented for any tool. LLMs cannot plan downstream calls or extract required fields. Responses are unstructured.
Parameter descriptions are missing or generic. 'parameters' in list_product_names_mock lacks detail on what parameters are valid. 'request_data' in handle_mcp_request is vague.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 42 | <=2025-11-25 | v2 |
The 'request' tool exposes low-level HTTP details (method, endpoint, section enum). This violates abstraction, agents should not reason about HTTP verbs or API paths. Wrap this in domain-specific tools.
Mock tool naming ('list_product_names_mock') is non-standard and confusing. Either remove mock tools before production or use a consistent naming convention (e.g. 'list_products_demo'). LLMs may select the wrong variant.