Skip to main content
Glama
stefanskiasan

Azure DevOps MCP Server for Cline

list_projects

Retrieve all projects from your Azure DevOps organization to manage development workflows and access repositories.

Instructions

List all projects in the Azure DevOps organization

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The core handler function that initializes the Azure DevOps connection, fetches projects using the Core API, and returns them as JSON text content.
    export async function listProjects(args: Record<string, unknown> | undefined, config: AzureDevOpsConfig) {
      AzureDevOpsConnection.initialize(config);
      const connection = AzureDevOpsConnection.getInstance();
      const coreApi = await connection.getCoreApi();
    
      try {
        const projects = await coreApi.getProjects();
    
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(projects, null, 2),
            },
          ],
        };
      } catch (error: unknown) {
        if (error instanceof McpError) throw error;
        const errorMessage = error instanceof Error ? error.message : 'Unknown error';
        throw new McpError(
          ErrorCode.InternalError,
          `Failed to list projects: ${errorMessage}`
        );
      }
    }
  • Input schema definition for the list_projects tool, specifying an empty object with no required properties.
    inputSchema: {
      type: 'object',
      properties: {},
      required: [],
    },
  • Tool definition registration including name, description, and schema, exported for use in the project tools module.
    const definitions = [
      {
        name: 'list_projects',
        description: 'List all projects in the Azure DevOps organization',
        inputSchema: {
          type: 'object',
          properties: {},
          required: [],
        },
      },
    ];
  • src/index.ts:153-155 (registration)
    Switch case in the main tool call handler that dispatches to the listProjects function for the 'list_projects' tool.
    case 'list_projects':
      result = await tools.project.listProjects(request.params.arguments);
      break;
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action ('List all projects') but lacks details on permissions, rate limits, pagination, or response format. For a read operation with zero annotation coverage, this is a significant gap in transparency.

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?

The description is a single, clear sentence with zero waste. It's front-loaded and efficiently conveys the core purpose without redundancy or fluff, making it highly concise and well-structured.

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

Completeness3/5

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

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is adequate as a basic read operation. However, it lacks context on behavioral aspects like permissions or output format, which could be helpful for an agent, keeping it at a minimum viable level.

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

Parameters4/5

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

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate, earning a baseline score of 4 for not introducing unnecessary information.

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

Purpose4/5

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

The description clearly states the verb ('List') and resource ('projects in the Azure DevOps organization'), making the purpose unambiguous. However, it doesn't distinguish this tool from siblings like 'list_pipelines' or 'list_work_items' beyond the resource name, which is why it doesn't reach a perfect score.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, context, or exclusions, such as whether this lists all projects unconditionally or if there are filtering options elsewhere. This leaves the agent without usage direction.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/stefanskiasan/azure-devops-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server