No user-submitted related servers found.
Scored across 47 tools
Every tool targets a distinct resource and action; where domains overlap (work item vs document vs test record attachments), descriptions explicitly cross-reference their siblings. The read_/get_ split is clearly delineated, and enum/recipe helpers are unambiguously separate.
All tools follow a consistent verb_noun snake_case pattern with clear singular/plural conventions (get single, list/update/create bulk). Prepositional verbs like move_work_item_to_document are used uniformly.
At 47 tools this is far above the well-scoped 3-15 range; even though the tools organize into per-resource families, the sheer number makes selection costly and could overwhelm agents.
Core lifecycle coverage for work items, documents, test runs/records, attachments, comments, and links is solid, with enum lookup and HTML/SQL recipe helpers that close write-path gaps. However, deletion is only available for links; attachments, comments, documents, and work items have no delete tool, which could create dead ends.