Skip to main content
Glama
ennuiii

Azure DevOps MCP Server with PAT Authentication

by ennuiii

testplan_list_test_plans

Retrieve a paginated list of test plans from an Azure DevOps project. Filter for active plans and toggle detailed information to streamline test management.

Instructions

Retrieve a paginated list of test plans from an Azure DevOps project. Allows filtering for active plans and toggling detailed information.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
continuationTokenNoToken to continue fetching test plans from a previous request.
filterActivePlansNoFilter to include only active test plans. Defaults to true.
includePlanDetailsNoInclude detailed information about each test plan.
projectYesThe unique identifier (ID or name) of the Azure DevOps project.

Implementation Reference

  • The handler function that executes the tool: fetches test plans from Azure DevOps TestPlanApi using provided parameters.
    async ({ project, filterActivePlans, includePlanDetails, continuationToken }) => {
      const owner = ""; //making owner an empty string untill we can figure out how to get owner id
      const connection = await connectionProvider();
      const testPlanApi = await connection.getTestPlanApi();
    
      const testPlans = await testPlanApi.getTestPlans(project, owner, continuationToken, includePlanDetails, filterActivePlans);
    
      return {
        content: [{ type: "text", text: JSON.stringify(testPlans, null, 2) }],
      };
    }
  • Zod schema defining input parameters for the tool.
    {
      project: z.string().describe("The unique identifier (ID or name) of the Azure DevOps project."),
      filterActivePlans: z.boolean().default(true).describe("Filter to include only active test plans. Defaults to true."),
      includePlanDetails: z.boolean().default(false).describe("Include detailed information about each test plan."),
      continuationToken: z.string().optional().describe("Token to continue fetching test plans from a previous request."),
    },
  • The server.tool registration call that defines the tool name, description, input schema, and handler function.
    server.tool(
      Test_Plan_Tools.list_test_plans,
      "Retrieve a paginated list of test plans from an Azure DevOps project. Allows filtering for active plans and toggling detailed information.",
      {
        project: z.string().describe("The unique identifier (ID or name) of the Azure DevOps project."),
        filterActivePlans: z.boolean().default(true).describe("Filter to include only active test plans. Defaults to true."),
        includePlanDetails: z.boolean().default(false).describe("Include detailed information about each test plan."),
        continuationToken: z.string().optional().describe("Token to continue fetching test plans from a previous request."),
      },
      async ({ project, filterActivePlans, includePlanDetails, continuationToken }) => {
        const owner = ""; //making owner an empty string untill we can figure out how to get owner id
        const connection = await connectionProvider();
        const testPlanApi = await connection.getTestPlanApi();
    
        const testPlans = await testPlanApi.getTestPlans(project, owner, continuationToken, includePlanDetails, filterActivePlans);
    
        return {
          content: [{ type: "text", text: JSON.stringify(testPlans, null, 2) }],
        };
      }
    );
  • Constant object defining string names for test plan related tools, including 'testplan_list_test_plans'.
    const Test_Plan_Tools = {
      create_test_plan: "testplan_create_test_plan",
      create_test_case: "testplan_create_test_case",
      add_test_cases_to_suite: "testplan_add_test_cases_to_suite",
      test_results_from_build_id: "testplan_show_test_results_from_build_id",
      list_test_cases: "testplan_list_test_cases",
      list_test_plans: "testplan_list_test_plans",
    };
  • src/tools.ts:27-27 (registration)
    Invocation of configureTestPlanTools within the main tools configuration, which registers the testplan_list_test_plans tool among others.
    configureTestPlanTools(server, tokenProvider, connectionProvider);
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions pagination and filtering options, which is helpful, but fails to cover critical aspects like whether this is a read-only operation (implied but not stated), potential rate limits, authentication requirements, error handling, or the structure of returned data. For a list operation with no annotation coverage, this leaves significant gaps.

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

Conciseness4/5

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

The description is a single, well-structured sentence that efficiently conveys the core functionality and key features (paginated list, filtering, detailed info). It's front-loaded with the main purpose and avoids unnecessary words, though it could be slightly more concise by integrating the filtering details more seamlessly.

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 moderate complexity (list operation with filtering), 100% schema coverage helps, but the lack of annotations and output schema means the description should do more. It covers the basic purpose and parameters but misses behavioral details (e.g., pagination mechanics, error cases) and output expectations, making it adequate but incomplete for full agent understanding.

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 input schema has 100% description coverage, so the schema already documents all parameters thoroughly. The description adds minimal value by mentioning filtering for active plans and detailed information, which aligns with the schema but doesn't provide additional semantic context beyond what's already in the parameter descriptions.

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 paginated list') and resource ('test plans from an Azure DevOps project'), making the purpose evident. However, it doesn't explicitly differentiate this tool from its sibling tools (like testplan_list_test_cases), 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 mentions filtering capabilities ('allows filtering for active plans and toggling detailed information'), which provides some implied context for usage. However, it lacks explicit guidance on when to use this tool versus alternatives (e.g., other testplan_* tools or search tools), and doesn't mention prerequisites or exclusions.

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