Loading ToolBench
MCP server for C2C instant resale marketplace operations, providing AI-powered pricing suggestions, sale probability estimation, and prepaid shipping label generation for preloved items
This server has a single tool 'execute_skill_action' with critical definition gaps. The tool description exists but is generic (89 chars, below the 194-char baseline for production tools). No input schema is visible in the source code, the mcp_server.py file only prints a JSON status message and does not register the tool with parameters, types, or constraints. The client.py file shows a hardcoded example method but no actual tool parameter definitions. Without visible schema, the tool cannot be properly invoked by an LLM. The server does not implement any of the 54 Agentic Tool Patterns: no error handling guidance, no parameter descriptions, no output schema documentation, no pagination, no idempotency markers, and no security controls.
Execute skill action for C2C instant resale operations including AI pricing, sale probability estimation, and shipping label generation
No input schema visible. Tool parameters, types, and constraints are not defined in mcp_server.py. The tool cannot be invoked by an LLM without a formal schema.
Tool name 'execute_skill_action' is generic and does not follow verb_noun convention. It does not clearly convey what action is executed (pricing? shipping? both?). Ambiguous names cause LLMs to guess wrong.
Tool description (89 chars) is below the 194-char production baseline and lacks critical context: WHAT does it do? WHEN should the LLM call it? WHAT does it return? Current description does not answer these questions.
No output schema documented. The client.py example shows a hardcoded response structure, but the tool definition does not declare what fields the LLM should expect. LLMs cannot plan downstream calls without knowing the response shape.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 21 | 2026-07-28+ | v2 |
No error handling or recovery guidance. If the tool fails (invalid item, API timeout, pricing service down), the LLM has no actionable error message or next steps. Errors must tell the agent what to do.