Skip to main content
Glama
ennuiii

Azure DevOps MCP Server with PAT Authentication

by ennuiii

core_list_project_teams

Retrieve a list of teams for a specific Azure DevOps project, with options to filter by user membership, paginate results, and limit the number of teams returned.

Instructions

Retrieve a list of teams for the specified Azure DevOps project.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mineNoIf true, only return teams that the authenticated user is a member of.
projectYesThe name or ID of the Azure DevOps project.
skipNoThe number of teams to skip for pagination. Defaults to 0.
topNoThe maximum number of teams to return. Defaults to 100.

Implementation Reference

  • The handler function that executes the tool logic: connects to Azure DevOps CoreApi, fetches teams for the given project (optionally filtering by membership, paginated), returns JSON string or error.
    async ({ project, mine, top, skip }) => {
      try {
        const connection = await connectionProvider();
        const coreApi = await connection.getCoreApi();
        const teams = await coreApi.getTeams(project, mine, top, skip, false);
    
        if (!teams) {
          return { content: [{ type: "text", text: "No teams found" }], isError: true };
        }
    
        return {
          content: [{ type: "text", text: JSON.stringify(teams, null, 2) }],
        };
      } catch (error) {
        const errorMessage = error instanceof Error ? error.message : "Unknown error occurred";
    
        return {
          content: [{ type: "text", text: `Error fetching project teams: ${errorMessage}` }],
          isError: true,
        };
      }
    }
  • Input schema using Zod for validating tool parameters: project (string, required), mine/top/skip (optional).
    {
      project: z.string().describe("The name or ID of the Azure DevOps project."),
      mine: z.boolean().optional().describe("If true, only return teams that the authenticated user is a member of."),
      top: z.number().optional().describe("The maximum number of teams to return. Defaults to 100."),
      skip: z.number().optional().describe("The number of teams to skip for pagination. Defaults to 0."),
    },
  • Registration of the 'core_list_project_teams' tool on the McpServer, including description, schema, and handler.
    server.tool(
      CORE_TOOLS.list_project_teams,
      "Retrieve a list of teams for the specified Azure DevOps project.",
      {
        project: z.string().describe("The name or ID of the Azure DevOps project."),
        mine: z.boolean().optional().describe("If true, only return teams that the authenticated user is a member of."),
        top: z.number().optional().describe("The maximum number of teams to return. Defaults to 100."),
        skip: z.number().optional().describe("The number of teams to skip for pagination. Defaults to 0."),
      },
      async ({ project, mine, top, skip }) => {
        try {
          const connection = await connectionProvider();
          const coreApi = await connection.getCoreApi();
          const teams = await coreApi.getTeams(project, mine, top, skip, false);
    
          if (!teams) {
            return { content: [{ type: "text", text: "No teams found" }], isError: true };
          }
    
          return {
            content: [{ type: "text", text: JSON.stringify(teams, null, 2) }],
          };
        } catch (error) {
          const errorMessage = error instanceof Error ? error.message : "Unknown error occurred";
    
          return {
            content: [{ type: "text", text: `Error fetching project teams: ${errorMessage}` }],
            isError: true,
          };
        }
      }
    );
  • Constant object mapping internal names to MCP tool names, used in registration.
    const CORE_TOOLS = {
      list_project_teams: "core_list_project_teams",
      list_projects: "core_list_projects",
      get_identity_ids: "core_get_identity_ids",
    };
  • src/tools.ts:20-20 (registration)
    Invocation of configureCoreTools which registers the core tools including core_list_project_teams.
    configureCoreTools(server, tokenProvider, connectionProvider, userAgentProvider);
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions retrieval but lacks behavioral details: it doesn't specify authentication requirements, rate limits, pagination behavior (beyond schema hints), error conditions, or what the returned list includes (e.g., team IDs, names, members). This is inadequate for a tool with parameters and no output schema.

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 wasted words. It's front-loaded with the core purpose and efficiently specifies the resource context. Every element earns its place without redundancy.

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

Completeness2/5

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

Given 4 parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain return values (e.g., list format, fields), error handling, or behavioral constraints like authentication. For a retrieval tool with pagination parameters, this leaves significant gaps for an agent to use it correctly.

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%, so the schema fully documents all parameters. The description adds no parameter-specific information beyond implying the 'project' parameter is required. Baseline 3 is appropriate as the schema does the heavy lifting, but the description doesn't enhance understanding of parameter interactions or defaults.

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 ('retrieve a list') and resource ('teams for the specified Azure DevOps project'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'core_list_projects' or 'wit_list_backlogs' beyond the resource type, which prevents 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 (e.g., needing project access), compare to similar tools (e.g., 'wit_list_backlog_work_items' for work items), or specify use cases (e.g., team management vs. project overview).

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

Related 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/ennuiii/DevOpsMcpPAT'

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