No user-submitted related servers found.
Scored across 25 tools
Most tools target distinct resources (start/continue/reply/cancel/wait/result are clearly separable lifecycle ops), but several pairs have murky boundaries: tandem_review vs tandem_review_run, tandem_result vs tandem_wait, tandem_audit vs tandem_recommend (both share preview/hash/opt-in OpenRouter semantics), and tandem_project_context vs tandem_publish_artifact/read_artifact all move immutable shared data. Descriptions work hard to disambiguate, but the overlaps mean an agent can plausibly misselect.
All names use a consistent 'tandem_' prefix and snake_case, which is uniform and readable. There is a minor deviation between verb-first names (start, continue, cancel, list, wait, reply) and noun-first names (scope, team, result, channel, review, findings), but the pattern is predictable within categories and rarely ambiguous.
25 tools sits at the upper/heavy boundary. For a multi-stage orchestration system (tasks, teams, reviews, context exchange, delivery) many tools earn their place, but the surface is sprawling and includes peripheral operations (diagnose, channel, receipt, export/import) that push it toward overload.
Coverage is broad and thoughtful: task lifecycle (start/continue/wait/result/reply/cancel/list), context/artifact exchange (project_context, publish/read, export/import), review capture/run/findings, team, desktop, and delivery all have tools. The surface has few obvious dead ends; remaining gaps are edge operations rather than core workflow holes.