No user-submitted related servers found.
Scored across 19 tools
Tools target distinct resources (novels, chapters, short stories, local articles, auth) and single vs. batch operations are clearly separated. Minor overlap exists between get_publish_status and get_stats (both do environment self-checks) and between create_short_story_tomato and publish_short_story_tomato (both can create), but descriptions clarify the boundaries.
A predictable verb_noun pattern with a _tomato suffix for remote/backend tools and no suffix for local tools is largely followed (list_novels_tomato, create_short_story_tomato, save_article, delete_article). Deviations like set_tomato_cookies (tomato in the middle), batch_publish_chapters (missing suffix), and get_publish_status are minor but noticeable.
19 tools is on the heavier side but justified by the server's broad scope: authentication, novel creation, chapter upload (single + batch), short-story lifecycle, local article library, and diagnostics. Each tool earns its place, though the set could be trimmed slightly by merging the two diagnostic tools.
Core workflows are well covered: auth, novel creation, chapter publishing, batch upload, short-story CRUD + cover + publish, local article library CRUD, and status/stats. Gaps are minor — there is no update/edit for novels or chapters and no update for local articles, but the publishing lifecycle itself is complete.