Loading ToolBench
Self-hosted sharing platform for HTML, Markdown and text files with MCP integration
Renderbin exposes 10 file-management tools with basic naming and descriptions. All tools follow verb_noun convention (mcp_files_*), which is good. However, descriptions are uniformly terse (15 - 35 chars), falling well below the 50 - 200 char baseline for LLM-optimized docs. Input schemas are present for 8 of 10 tools but lack depth: parameters have type and description, but no enums, ranges, or format constraints. Output schemas are not documented anywhere in the source. Error handling is absent, no guidance on retryability, user-fixable vs fatal errors, or recovery paths. The two read-only tools (list, get) lack pagination parameters despite the pattern baseline requiring them for list operations. Overall, this is a functional but minimal implementation typical of early-stage MCP servers.
Create a new file with HTML content
Soft delete a file (move to trash)
Get a specific file by slug with full content
List files owned by the authenticated user
Restore a deleted file from trash
Search files by name or tags
Set expiration time or view limit for a file
Set tags for a file
Descriptions are uniformly terse (15 - 35 chars), far below the 50 - 200 char baseline. LLMs cannot determine when to select tools or understand prerequisites. E.g., 'List files owned by the authenticated user' lacks context on pagination, filtering, or return structure.
No output schemas documented. LLMs cannot plan downstream tool calls or extract required fields (e.g., does list return file IDs? slugs? both?). This violates the pattern baseline requiring 100% of A+ tools to have documented return types.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 46 | 2026-07-28+ | v2 |
Set file visibility to public or private
Update an existing file's content, name, slug, or access code
mcp_files_list and mcp_files_search lack pagination parameters (limit, offset, cursor). Without pagination, large result sets blow context windows. Pattern baseline requires paginated-result for list operations.
No error handling guidance. Tools do not document retryability, user-fixable vs fatal errors, or recovery paths. E.g., delete_file should explain: 'Soft delete is reversible; call restore_file to undo.' Pattern baseline requires error-classification and recovery-guide.
Parameters lack constraints. E.g., 'tags' is a free-form string with no format guidance; 'expires_at' has no validation hint (ISO 8601?); 'max_views' has no range (1 - 1000000?). Unconstrained params invite hallucinated values.