Loading ToolBench
Sell anything with a single photo via GenPark. Instantly turns an image into a live Stripe Checkout link.
This MCP server defines a single tool 'sell' with a basic schema and minimal description. The tool name lacks an action verb (should be 'create_storefront' or 'generate_storefront_link'), the description is vague about what 'Generate' means in practice, and there is no documented output schema. The input schema is present but sparse, parameters lack minimum/maximum constraints, format specifications, or detailed descriptions explaining valid values or error conditions. No error handling guidance is provided. This server would struggle in production use because agents cannot infer when to call it, what to expect in return, or how to recover from failures.
Generate a storefront and checkout link from a photo
Tool name 'sell' does not start with an action verb. Unclear whether it creates, updates, or deletes. Should be 'create_storefront', 'generate_checkout_link', or 'generate_sales_link' to clearly convey the action.
Tool description 'Generate a storefront and checkout link from a photo' is too brief (55 chars, below recommended 50 - 200 char range) and lacks context about prerequisites, output format, or when to use this tool vs alternatives. Does not explain what 'storefront' means or what API/service backs this call.
Input schema lacks descriptions for parameters. 'image' description only says 'Path to the product photo' without format requirements (file path? URL? base64?). 'price' has no range, precision, or currency interaction guidance. 'currency' lacks enum constraint, agents may hallucinate invalid codes.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 32 | 2026-07-28+ | v2 |
No output schema documented. Agents have no way to know what fields are returned (e.g., storefront_url, checkout_url, product_id, expiration). Without documented output, downstream tool chains cannot be planned and LLMs cannot extract necessary IDs for follow-up operations.
No error handling or recovery guidance. If the image upload fails, price validation fails, or the storefront generation times out, the agent has no guidance on what to do next or whether to retry.
Parameter 'image' is described as a 'Path' but no validation rules are provided. Is it a relative path? Absolute? URL? Does it accept http://, file://, or only local filesystem paths? This ambiguity will cause LLM errors.
Parameter 'currency' has a default 'usd' but lacks an enum constraint defining valid currency codes. Agents may pass invalid codes like 'usd_eur' or 'dollar'. Should declare valid codes as enum: ['usd', 'eur', 'gbp', ...] or reference ISO 4217.
Parameter 'price' lacks numeric constraints. No minimum (e.g., > 0), maximum, or decimal precision guidance. Agents may pass negative prices, zero, or thousands of decimal places, all of which could cause silent failures or unexpected behavior.