No user-submitted related servers found.
Scored across 27 tools
Descriptions are unusually thorough and explicitly cross-reference sibling tools (e.g. lore_profile_status points to lore_status and lore_configure; lore_workflow_status points to lore_workflow_history), which strongly aids selection. However, the large cluster of status/getter tools (lore_status, lore_story_status, lore_profile_status, lore_writer_status, lore_arc_status, lore_snapshot_status, lore_workflow_status) and the five *_decide tools create real overlap risk, and the generic lore_decide (for lore_write approvals) sits confusingly alongside the entity-scoped deciders.
Nearly all 27 tools use a consistent lore_<noun> / lore_<noun>_<verb> snake_case convention (lore_story_plan, lore_arc_decide, lore_writer_status). Minor deviations exist: bare-verb names like lore_write, lore_sync, lore_init, and the generic lore_decide breaks the otherwise predictable <entity>_decide pattern.
At 27 tools this is heavy and pushes past the comfortable 3-15 range, so the surface is broad and requires the agent to hold a lot of context. A novel-orchestration domain with distinct lifecycle stages can plausibly justify it, but several status/decide variants inflate the count beyond the strict minimum.
The lifecycle is well covered: profile, init/create, story spine, writer skill, arc planning, writing, approval, sync of manual edits, rollback, snapshots, configuration, style anchoring, and a webtoon branch, with status tools for each artifact. Minor gaps remain (e.g. no restore tool from rollback archives, webtoon only exposes a single scene tool), but core workflows have no dead ends.