Skip to main content
Glama
ennuiii

Azure DevOps MCP Server with PAT Authentication

by ennuiii

testplan_create_test_plan

Create a new test plan in Azure DevOps by specifying the project, name, iteration, and optional details like description, dates, and area path.

Instructions

Creates a new test plan in the project.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
areaPathNoThe area path for the test plan
descriptionNoThe description of the test plan
endDateNoThe end date of the test plan
iterationYesThe iteration path for the test plan
nameYesThe name of the test plan to be created.
projectYesThe unique identifier (ID or name) of the Azure DevOps project where the test plan will be created.
startDateNoThe start date of the test plan

Implementation Reference

  • The handler function that executes the tool logic: connects to Azure DevOps, prepares TestPlanCreateParams, calls testPlanApi.createTestPlan, and returns the created test plan as JSON.
    async ({ project, name, iteration, description, startDate, endDate, areaPath }) => {
      const connection = await connectionProvider();
      const testPlanApi = await connection.getTestPlanApi();
    
      const testPlanToCreate: TestPlanCreateParams = {
        name,
        iteration,
        description,
        startDate: startDate ? new Date(startDate) : undefined,
        endDate: endDate ? new Date(endDate) : undefined,
        areaPath,
      };
    
      const createdTestPlan = await testPlanApi.createTestPlan(testPlanToCreate, project);
    
      return {
        content: [{ type: "text", text: JSON.stringify(createdTestPlan, null, 2) }],
      };
    }
  • Zod schema defining the input parameters for creating a test plan: project, name, iteration, optional description, dates, and areaPath.
      project: z.string().describe("The unique identifier (ID or name) of the Azure DevOps project where the test plan will be created."),
      name: z.string().describe("The name of the test plan to be created."),
      iteration: z.string().describe("The iteration path for the test plan"),
      description: z.string().optional().describe("The description of the test plan"),
      startDate: z.string().optional().describe("The start date of the test plan"),
      endDate: z.string().optional().describe("The end date of the test plan"),
      areaPath: z.string().optional().describe("The area path for the test plan"),
    },
  • The server.tool registration call that registers the 'testplan_create_test_plan' tool with its description, input schema, and inline handler function.
    Test_Plan_Tools.create_test_plan,
    "Creates a new test plan in the project.",
    {
      project: z.string().describe("The unique identifier (ID or name) of the Azure DevOps project where the test plan will be created."),
      name: z.string().describe("The name of the test plan to be created."),
      iteration: z.string().describe("The iteration path for the test plan"),
      description: z.string().optional().describe("The description of the test plan"),
      startDate: z.string().optional().describe("The start date of the test plan"),
      endDate: z.string().optional().describe("The end date of the test plan"),
      areaPath: z.string().optional().describe("The area path for the test plan"),
    },
    async ({ project, name, iteration, description, startDate, endDate, areaPath }) => {
      const connection = await connectionProvider();
      const testPlanApi = await connection.getTestPlanApi();
    
      const testPlanToCreate: TestPlanCreateParams = {
        name,
        iteration,
        description,
        startDate: startDate ? new Date(startDate) : undefined,
        endDate: endDate ? new Date(endDate) : undefined,
        areaPath,
      };
    
      const createdTestPlan = await testPlanApi.createTestPlan(testPlanToCreate, project);
    
      return {
        content: [{ type: "text", text: JSON.stringify(createdTestPlan, null, 2) }],
      };
    }
Behavior2/5

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

With no annotations provided, the description carries full burden but only states it 'creates' without detailing behavioral aspects like required permissions, whether it's idempotent, error handling, or what happens on success. This is inadequate for a mutation tool with zero annotation coverage.

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 with no wasted words. It's appropriately sized and front-loaded, clearly stating the core function without unnecessary elaboration.

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?

For a creation tool with 7 parameters, no annotations, and no output schema, the description is insufficient. It lacks behavioral context, usage guidelines, and details about the creation process, making it incomplete for effective tool invocation.

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 7 parameters. The description adds no parameter-specific information beyond implying a 'project' context, meeting the baseline for high schema coverage without extra value.

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 ('Creates') and resource ('new test plan in the project'), making the purpose unambiguous. However, it doesn't differentiate from sibling tools like 'testplan_list_test_plans' or 'testplan_create_test_case', which would require a 5.

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?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites, constraints, or sibling tools like 'testplan_list_test_plans' for viewing existing plans, leaving usage context unclear.

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