No user-submitted related servers found.
Scored across 21 tools
Each tool serves a clearly distinct purpose in workspace management, module design, entry CRUD, file handling, or mode switching. The descriptions provide explicit workflow guidance, eliminating ambiguity between similar operations like submit_activity and submit_activities.
All 21 tool names follow a consistent verb_noun snake_case pattern with verbs like list, get, set, submit, upload, etc. No mixing of conventions, making it easy for an agent to predict tool names.
With 21 tools, the count falls into the borderline range (16-25) per the scoring guidelines. While the server covers a comprehensive domain, the number feels slightly heavy for typical MCP servers, which usually have 3-15 tools.
The tool surface covers the full lifecycle: workspace selection, module creation (design, validate, create), entry CRUD (list, get, form, submit, history), and file upload/download. Minor gaps exist, such as no dedicated tool for deleting entries (handled via submit_activity) and no export functionality, but agents can work around these.