Skip to main content
Glama
Sign In
Azure DevOps MCP Server

Azure DevOps MCP Server

by bugzy-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

azuredevops_list_projects

List all projects in an Azure DevOps organization to discover available projects when the name is unknown or verify that a project exists.

Instructions

List all projects in the Azure DevOps organization. Use this to discover available projects when the project name is not known or to verify a project exists.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "azuredevops_list_projects"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNoMaximum number of projects to return (default: 100, max: 100)
skipNoNumber of projects to skip for pagination (default: 0)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the burden but only asserts read-oriented discovery intent. It doesn't disclose return shape (names vs. ids), auth/permission requirements, or pagination behavior — the latter is only implied by the schema's top/skip. Also, 'List all projects' sits awkwardly against a hard 100-item cap, though the schema itself makes that limit explicit.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences, zero filler, with the core operation front-loaded before the routing guidance. Every clause earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple no-argument read tool with fully documented params and no output schema, the description covers purpose and usage motivation adequately. It could mention auth expectations or the 100-result cap, but nothing essential to invoking it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%: both 'top' and 'skip' are documented with defaults, bounds, and pagination purpose. The description adds no syntax or format detail beyond the schema, so the baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('List') and resource ('all projects in the Azure DevOps organization'), which is unambiguous. The sibling tools all operate on work items, so this project-discovery tool is trivially distinguishable without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says when to use it: 'when the project name is not known or to verify a project exists.' No alternatives are named, but no sibling competes for this job, so the guidance is effectively complete rather than needing exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools