Loading ToolBench
MCP server for Better Fullstack - a configurable fullstack project scaffolder. Exposes tools for getting guidance, checking compatibility, planning projects, creating projects, planning stack updates, applying stack updates, planning additions, and adding features.
Server has 9 tools with basic naming (verb_noun pattern) and descriptions present, but significant gaps in schema completeness, parameter documentation, and error handling. All tools lack detailed input parameter descriptions beyond type declarations. No output schemas documented. Descriptions are generic (avg ~60 chars) and lack context on when/why to use each tool. No error recovery guidance. Parameter schemas show types but lack constraints, enums, or validation rules. Tools like bfs_check_compatibility and bfs_plan_stack_update accept generic 'object' types with no field documentation, forcing LLMs to guess structure.
Add a new feature or component to an existing project
Apply stack updates to an existing project
Check compatibility of selected technologies in a stack configuration
Create a new fullstack project with specified configuration
Get guidance on stack selection and project configuration
Get the schema for stack configuration and project structure
Plan adding a new feature or component to an existing project
Plan a new fullstack project with specified configuration
Generic 'object' parameters lack field documentation. bfs_check_compatibility, bfs_plan_project, bfs_create_project, bfs_plan_stack_update, bfs_apply_stack_update, and bfs_add_feature all accept 'stack' or 'stackChanges' or 'featureConfig' as bare objects with no schema of required/optional fields, types, or constraints. LLMs cannot infer valid structure.
No output schemas documented. Tools return results but LLMs have no visibility into response structure, field types, or what data is available for downstream tool calls. Breaks tool chaining.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 51 | 2026-07-28+ | v2 |
Plan updates to an existing project's stack configuration
Parameter descriptions are missing or trivial. 'stack' is described only as 'Stack configuration' with no detail on required fields, valid values, or format. 'projectPath' lacks guidance on absolute vs relative paths, symlink handling, or validation.
No error handling or recovery guidance. Tools do not document what errors can occur, whether they are retryable, or what the LLM should do next. No actionable error messages visible in code.
Destructive tools (bfs_create_project, bfs_apply_stack_update, bfs_add_feature) lack confirmation or dry-run support. No mechanism to preview changes before writing to disk. High risk of accidental data loss.