No user-submitted related servers found.
Scored across 20 tools
Tools largely target distinct resources and lifecycle steps, and the descriptions explicitly separate similar-looking operations. A few pairs remain easy to confuse—next/prompts/state all surface pending work, and search/find_evidence both retrieve evidence—but the descriptions usually resolve the choice.
All tools use the same forbiz_ prefix and snake_case, with no casing or abbreviation chaos. The only inconsistency is that some names are verb phrases (forbiz_commit, forbiz_get_action) while others are noun-like views (forbiz_state, forbiz_agents), so the pattern is readable but not uniformly verb_noun.
20 tools is on the heavy side for an MCP server and pushes the practical limit before agents must sift through many closely related lifecycle calls. While most tools map to distinct operations, some read-only views and status checks could arguably be consolidated.
The core action lifecycle is well covered: commit, execute, check/record signal, postpone, close, close-without-signal, history, and detail. Evidence and workspace bootstrap/ownership are also present, and the generic forbiz_request escape hatch prevents dead ends for projects, decisions, and other API routes, though those domains lack dedicated tools.