Loading ToolBench
Azure DevOps reference server for the Model Context Protocol (MCP)
Server has 29 tools with basic naming (verb_noun pattern mostly followed) and descriptions present. However, critical gaps exist: parameter descriptions are largely absent or minimal, input schemas are not visible in the provided source code excerpt, and output schemas are undocumented. The code shows tool registration via zodToJsonSchema but the actual Zod schema definitions are imported from feature modules not included in the excerpt. Without seeing the full schema definitions, parameter types, and constraints, schema quality cannot be verified. Error handling is not evident in the sample. Descriptions are adequate (50-150 chars typical) but lack dependency hints and recovery guidance. No tool annotations (readOnlyHint, destructiveHint) visible despite 8 WRITE tools that should be marked destructive.
Add a comment to a pull request (reply to existing comments or create new threads)
Create a new pull request
Create a new wiki in the project
Create a new work item
Displays a hierarchical tree view of files and directories across multiple Azure DevOps repositories within a project, based on their default branches
Get content of a file or directory from a repository
Input schemas not visible in source excerpt. All 29 tools reference zodToJsonSchema() but actual Zod schema definitions (GetMeSchema, ListOrganizationsSchema, etc.) are imported from feature modules not provided. Cannot verify parameter types, constraints, or descriptions.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 41 | 2026-07-28+ | v2 |
Get details of the authenticated user (id, displayName, email)
Get details of a specific pipeline
Get details of a specific project
Get comprehensive details of a project including process, work item types, and teams
Get comments from a specific pull request
Get details of a specific repository
Get detailed information about a repository including statistics and refs
Get the content of a wiki page
Get details of wikis in a project
Get details of a specific work item
List all Azure DevOps organizations accessible to the current authentication
List pipelines in a project
List all projects in an organization
List pull requests in a repository
List repositories in a project
List work items in a project
Add or remove a link between work items
Search for code across repositories in a project
Search for content across wiki pages in a project
Search for work items across projects in Azure DevOps
Trigger a pipeline run
Update content of a wiki page
Update an existing work item
No tool annotations (readOnlyHint, destructiveHint, idempotentHint) present. 8 WRITE tools (create_work_item, update_work_item, manage_work_item_link, trigger_pipeline, create_pull_request, add_pull_request_comment, create_wiki, update_wiki_page) should be marked destructiveHint=true to signal irreversibility to agents.
Output schemas not documented. No indication of what fields are returned, pagination support, or chaining IDs. E.g., list_work_items should document whether it returns pagination metadata, total count, and whether results include IDs needed for downstream get_work_item calls.
Descriptions lack recovery guidance and dependency hints. E.g., 'List work items in a project' does not explain when to call this vs search_work_items, what structure is returned, or whether pagination is supported. Descriptions should be 50-200 chars and include WHEN to use the tool.
No error handling or recovery guidance visible. Tools do not document what errors can occur, whether they are retryable, or what the agent should do next. E.g., create_work_item should document validation errors and guide the agent to call list_work_items to see valid work item types.