Skip to main content
Glama
aliyun

AlibabaCloud DevOps MCP Server

Official
by aliyun

create_sprint

Create a new sprint in Alibaba Cloud DevOps projects to organize work items, assign owners, set timelines, and manage development cycles for efficient project delivery.

Instructions

[Project Management] Create a new sprint

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
organizationIdYesOrganization ID
projectIdYesProject unique identifier
nameYesSprint name
ownersYesSprint owner user IDs
startDateNoDate string in YYYY-MM-DD format
endDateNoDate string in YYYY-MM-DD format
descriptionNoSprint description
capacityHoursNoSprint capacity hours

Implementation Reference

  • Tool handler switch case that parses input, calls createSprintFunc, and returns JSON response.
    case "create_sprint": {
      const args = types.CreateSprintSchema.parse(request.params.arguments);
      const sprintResult = await sprint.createSprintFunc(
        args.organizationId,
        args.projectId,
        args.name,
        args.owners,
        args.startDate,
        args.endDate,
        args.description,
        args.capacityHours
      );
      return {
        content: [{ type: "text", text: JSON.stringify(sprintResult, null, 2) }],
      };
    }
  • Zod schema defining input parameters for create_sprint tool.
    export const CreateSprintSchema = z.object({
      organizationId: z.string().describe("Organization ID"),
      projectId: z.string().describe("Project unique identifier"),
      name: z.string().describe("Sprint name"),
      owners: z.array(z.string()).describe("Sprint owner user IDs"),
      startDate: z.string().optional().describe("Date string in YYYY-MM-DD format"),
      endDate: z.string().optional().describe("Date string in YYYY-MM-DD format"),
      description: z.string().optional().describe("Sprint description"),
      capacityHours: z.number().int().optional().describe("Sprint capacity hours"),
    });
  • Tool registration including name, description, and input schema reference.
    {
      name: "create_sprint",
      description: "[Project Management] Create a new sprint",
      inputSchema: zodToJsonSchema(types.CreateSprintSchema),
    },
  • Core function that makes the API request to create a sprint via Yunxiao API.
    export async function createSprintFunc(
      organizationId: string,
      projectId: string,
      name: string,
      owners: string[],
      startDate?: string,
      endDate?: string,
      description?: string,
      capacityHours?: number,
      operatorId?: string
    ): Promise<{ id: string }> {
      const url = `/oapi/v1/projex/organizations/${organizationId}/projects/${projectId}/sprints`;
    
      const requestBody: Record<string, any> = {
        name,
        owners,
      };
    
      if (startDate !== undefined) {
        requestBody.startDate = startDate;
      }
    
      if (endDate !== undefined) {
        requestBody.endDate = endDate;
      }
    
      if (description !== undefined) {
        requestBody.description = description;
      }
    
      if (capacityHours !== undefined) {
        requestBody.capacityHours = capacityHours;
      }
    
      if (operatorId !== undefined) {
        requestBody.operatorId = operatorId;
      }
    
      const response = await yunxiaoRequest(url, {
        method: "POST",
        body: requestBody,
      });
    
      return CreateSprintResponseSchema.parse(response);
    }
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 states the tool creates a sprint but fails to mention critical details like required permissions, whether it's idempotent, what happens on failure, or the response format. This leaves significant gaps for a mutation tool.

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 very brief—just two phrases—with no wasted words, making it efficient. However, it could be more front-loaded by integrating the domain context directly into the action statement for better clarity.

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 mutation tool with 8 parameters, no annotations, and no output schema, the description is insufficient. It lacks details on behavioral traits, error handling, and return values, leaving the agent with incomplete guidance for proper 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?

The input schema has 100% description coverage, clearly documenting all 8 parameters and their types. The description adds no additional parameter information beyond what the schema provides, so it meets the baseline score of 3 for adequate but not enhanced semantics.

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

Purpose3/5

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

The description states the action ('Create a new sprint') and includes a domain context tag ('[Project Management]'), which clarifies the tool's general purpose. However, it lacks specificity about what a sprint entails in this system and does not differentiate from sibling tools like 'create_work_item' or 'update_sprint', making it somewhat vague.

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, such as 'update_sprint' for modifying existing sprints or 'list_sprints' for viewing them. It also omits prerequisites, like needing an existing project or organization, 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

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/aliyun/alibabacloud-devops-mcp-server'

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