Skip to main content
Glama
aliyun

AlibabaCloud DevOps MCP Server

Official
by aliyun
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

update_sprint

Modify sprint details like name, dates, owners, and capacity in Alibaba Cloud DevOps projects to adjust project timelines and team assignments.

Instructions

[Project Management] Update an existing sprint

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
organizationIdYesOrganization ID
projectIdYesProject unique identifier
idYesSprint unique identifier
nameYesSprint name
ownersNoSprint 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-handlers/project-management.ts:90-106 (handler)
    Handler for 'update_sprint' tool: parses input with UpdateSprintSchema, calls updateSprintFunc from sprint module, returns success message.
    case "update_sprint": {
  const args = types.UpdateSprintSchema.parse(request.params.arguments);
  await sprint.updateSprintFunc(
    args.organizationId,
    args.projectId,
    args.id,
    args.name,
    args.owners,
    args.startDate,
    args.endDate,
    args.description,
    args.capacityHours
  );
  return {
    content: [{ type: "text", text: "Sprint updated successfully" }],
  };
}
  • operations/projex/sprint.ts:108-154 (helper)
    Core implementation of sprint update: constructs PUT request to Yunxiao API endpoint /oapi/v1/projex/organizations/{org}/projects/{proj}/sprints/{id} with provided fields.
    export async function updateSprintFunc(
  organizationId: string,
  projectId: string,
  id: string,
  name: string,
  owners?: string[],
  startDate?: string,
  endDate?: string,
  description?: string,
  capacityHours?: number,
  operatorId?: string
): Promise<void> {
  const url = `/oapi/v1/projex/organizations/${organizationId}/projects/${projectId}/sprints/${id}`;

  const requestBody: Record<string, any> = {
    name,
  };

  if (owners !== undefined) {
    requestBody.owners = 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;
  }

  await yunxiaoRequest(url, {
    method: "PUT",
    body: requestBody,
  });
}
  • operations/projex/types.ts:122-132 (schema)
    Zod schema for validating input parameters to update_sprint tool.
    export const UpdateSprintSchema = z.object({
  organizationId: z.string().describe("Organization ID"),
  projectId: z.string().describe("Project unique identifier"),
  id: z.string().describe("Sprint unique identifier"),
  name: z.string().describe("Sprint name"),
  owners: z.array(z.string()).optional().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-registry/project-management.ts:35-38 (registration)
    Tool registration in project-management registry: defines name, description, and input schema.
      name: "update_sprint",
  description: "[Project Management] Update an existing sprint",
  inputSchema: zodToJsonSchema(types.UpdateSprintSchema),
},

Tool Definition Quality

C2.7/5.0
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 states this is an update operation, implying mutation, but doesn't disclose behavioral traits such as required permissions, whether changes are reversible, error handling, or rate limits. The description is minimal and misses critical context 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.

Conciseness5/5

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

The description is extremely concise with a single sentence, front-loaded with the core action. There's no wasted text, making it efficient, though this conciseness comes at the cost of completeness. Every word earns its place.

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 the complexity (mutation tool with 9 parameters, no annotations, no output schema), the description is incomplete. It lacks details on behavior, error cases, return values, and usage context. For a tool that modifies data, this minimal description is insufficient to guide an agent effectively.

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 already documents all 9 parameters with descriptions. The description adds no meaning beyond the schema, such as explaining relationships between parameters (e.g., organizationId and projectId hierarchy) or usage examples. Baseline 3 is appropriate when schema does the heavy lifting.

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 ('Update') and resource ('an existing sprint'), which is clear but vague. It doesn't specify what fields can be updated or distinguish this tool from other update tools like update_work_item or update_file, though the resource type is different. It's not tautological but lacks specificity.

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 an existing sprint), exclusions, or compare it to sibling tools like create_sprint or get_sprint. Usage is implied from the name but not explicitly stated.

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