Spring Boot MCP Protocol Server for Azure DevOps integration, providing tools for interacting with Azure DevOps APIs including projects, work items, pipelines, repositories, and more.
Azure DevOps Companion MCP exhibits significant definition quality gaps across all tools. While schemas are present, descriptions are minimal (most under 100 chars), parameter descriptions lack actionable detail, and error handling guidance is absent. The server provides basic tool registration but falls well below production standards for LLM-optimized tool definitions. No evidence of validation rules, dependency hints, or recovery guidance in any tool.
Lista cuentas (Accounts) o devuelve el detalle de una cuenta por ID
Obtiene el memberId (GUID) del usuario autenticado desde Profiles (VSSPS)
Obtiene niveles de backlog o work items asociados en Azure DevOps
Lista los tableros de un equipo o proyecto en Azure DevOps. Requiere 'project' (string, obligatorio), 'team' (string, opcional), 'boardId' (string, opcional para obtener uno específico).
Generate a random UUID using java.util.UUID
Parameter descriptions lack actionable detail. Properties like 'accountId' lack examples of format, constraints, or when to use them. LLMs cannot infer whether a GUID, UUID, or numeric ID is required.
No error handling guidance. Tools provide no recovery instructions if a call fails (e.g., 'Project not found. Try search_projects() with a partial name.'). Agents cannot self-correct on failures.
Descriptions are under 100 characters and lack WHEN guidance. 'Lista cuentas...' tells what the tool does but not when to call it vs. a similar tool, or what structure it returns. Average description length should be 194 chars (baseline).
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | D | 50 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 46 | 2025-06-18+ | v1 |
No output schema documentation. Tools do not document what fields are returned, field types, or chaining IDs needed for follow-up calls. LLMs cannot plan multi-tool sequences.
Spanish parameter descriptions ('Filtrar por GUID del propietario (list)') are not translated or supplemented with English. Multi-locale servers should provide English as the canonical language for tool definitions to ensure LLM compatibility.
Parameter 'team' is listed as optional in azuredevops_work_get_backlogs but required in required array. Inconsistent marking creates ambiguity for LLMs about whether a call will succeed without it.
Boolean parameter 'includeWorkItems' has no description explaining what 'work items' are, when to set it true vs. false, or impact on response size/cost.