Azure DevOps server has 18 tools with basic schemas and descriptions, but significant gaps limit production readiness. All tools have descriptions (10-50 chars, mostly adequate) and input schemas with typed parameters. However, output schemas are completely undocumented, LLMs cannot predict what fields to expect from responses, breaking tool chaining. Parameter descriptions are minimal (5-20 chars) and lack constraints, ranges, or format guidance. No error handling guidance, no pagination support despite list operations, and no tool annotations. Naming is verb-first and clear (get_*, create_*, search_*), but parameter naming inconsistencies (project_id vs repository_id vs branch) create friction. STDIO transport caps protocol readiness at 50.
Add a comment to an existing issue
Create a new branch in a repository
Create or update a file in a repository
Create a new pull request
Create a new repository
Fork a repository to create a new copy
Get a list of branches for a repository
No output schemas documented. LLMs cannot predict response structure, breaking tool chaining and forcing agents to guess field names for downstream calls.
Parameter descriptions are minimal (5-20 chars) and lack format guidance, constraints, or ranges. E.g., 'top' parameter has no min/max bounds; 'branch' has no format specification.
No pagination support documented. List operations (get_projects, get_repositories, search_*) lack limit/offset/cursor parameters and total count returns, risking context window exhaustion.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 48 | 2026-07-28+ | v2 |
Get a list of commits for a branch
Get the content of a file
Get the contents of a file or directory
Get a list of Azure DevOps projects
Get a list of repositories for a project
Push multiple files to a repository in a single commit
Search for code in a repository
Search for users in the organization
Search for work items (issues, tasks, bugs) in a project
Update an existing branch to point to a new commit
Update the content of a file
No error handling guidance. Tools return raw API errors without recovery hints. E.g., 'Project not found' should suggest 'Call get_projects() to list available projects.'
No tool annotations (readOnlyHint, destructiveHint, idempotentHint). Agents cannot distinguish safe reads from destructive writes without reading descriptions.