Skip to main content
Glama
nikydobrev

Azure DevOps Multi-Organization MCP Server

by nikydobrev

list_projects

Retrieve all projects within a specified Azure DevOps organization to manage and organize development work across teams.

Instructions

Lists all projects in an Azure DevOps organization

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
organizationYesThe name of the Azure DevOps organization

Implementation Reference

  • The handler function for the 'list_projects' tool. It retrieves the connection for the specified organization, gets the Core API, fetches the projects, and returns them as JSON text or an error message.
    async ({ organization }) => {
      try {
        const connection = await connectionManager.getConnection(organization);
        const coreApi = await connection.getCoreApi();
        const projects = await coreApi.getProjects();
        return {
          content: [{ type: "text", text: JSON.stringify(projects, null, 2) }],
        };
      } catch (error: any) {
        return {
          content: [{ type: "text", text: `Error: ${error.message}` }],
          isError: true,
        };
      }
    }
  • Input schema for the 'list_projects' tool, requiring an 'organization' string parameter.
    {
      organization: z.string().describe("The name of the Azure DevOps organization"),
    },
  • Direct registration of the 'list_projects' tool using server.tool() within the registerOrganizationTools function.
    server.tool(
      "list_projects",
      "Lists all projects in an Azure DevOps organization",
      {
        organization: z.string().describe("The name of the Azure DevOps organization"),
      },
      async ({ organization }) => {
        try {
          const connection = await connectionManager.getConnection(organization);
          const coreApi = await connection.getCoreApi();
          const projects = await coreApi.getProjects();
          return {
            content: [{ type: "text", text: JSON.stringify(projects, null, 2) }],
          };
        } catch (error: any) {
          return {
            content: [{ type: "text", text: `Error: ${error.message}` }],
            isError: true,
          };
        }
      }
    );
  • src/tools/index.ts:8-8 (registration)
    Higher-level registration call to registerOrganizationTools from the main tools index, which includes the 'list_projects' tool.
    registerOrganizationTools(server, connectionManager);
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. While 'Lists' implies a read-only operation, it doesn't specify whether this requires authentication, what permissions are needed, whether results are paginated, or what the output format looks like. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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, efficient sentence that directly states the tool's purpose without unnecessary words. It's front-loaded with the core functionality, making it easy to parse quickly.

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 (1 parameter, no output schema, no annotations), the description is minimally adequate but lacks completeness. It doesn't address authentication requirements, output format, or how it fits with sibling tools, leaving the agent to infer these aspects. For a basic list operation, it meets the minimum threshold but could be more informative.

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?

The schema description coverage is 100%, with the single parameter 'organization' clearly documented in the schema. The description doesn't add any additional meaning beyond what's in the schema, such as explaining what constitutes a valid organization name or providing examples. With high schema coverage, the baseline score of 3 is appropriate.

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 action ('Lists') and resource ('all projects in an Azure DevOps organization'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'list_organizations' or 'git_list_repositories' by specifying what distinguishes a project from other Azure DevOps entities.

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 (e.g., authentication), when not to use it, or how it relates to sibling tools like 'list_organizations' or 'git_list_repositories' that might list different resource types.

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/nikydobrev/mcp-server-azure-devops-multi'

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