Skip to main content
Glama
aliyun

AlibabaCloud DevOps MCP Server

Official
by aliyun

list_sprints

Retrieve and filter sprints in an Alibaba Cloud DevOps project to track development progress and manage project timelines effectively.

Instructions

[Project Management] List sprints in a project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
organizationIdYesOrganization ID
idYesProject unique identifier
statusNoFilter by status: TODO, DOING, ARCHIVED
pageNoPage number
perPageNoPage size

Implementation Reference

  • Tool handler for 'list_sprints': parses input arguments using ListSprintsSchema, calls the listSprintsFunc helper, and returns the result as a JSON-formatted text response.
    case "list_sprints": {
      const args = types.ListSprintsSchema.parse(request.params.arguments);
      const sprints = await sprint.listSprintsFunc(
        args.organizationId,
        args.id,
        args.status,
        args.page,
        args.perPage
      );
      return {
        content: [{ type: "text", text: JSON.stringify(sprints, null, 2) }],
      };
    }
  • Core implementation of listing sprints: constructs API URL with query params for organization, project ID, status filter, pagination; makes GET request to Yunxiao API and parses response using SprintInfoSchema.
    export async function listSprintsFunc(
      organizationId: string,
      id: string,
      status?: string[],
      page?: number,
      perPage?: number
    ): Promise<z.infer<typeof SprintInfoSchema>[]> {
      const baseUrl = `/oapi/v1/projex/organizations/${organizationId}/projects/${id}/sprints`;
    
      const queryParams: Record<string, string | number | undefined> = {};
    
      if (status !== undefined && status.length > 0) {
        queryParams.status = status.join(',');
      }
    
      if (page !== undefined) {
        queryParams.page = page;
      }
    
      if (perPage !== undefined) {
        queryParams.perPage = perPage;
      }
    
      const url = buildUrl(baseUrl, queryParams);
    
      const response = await yunxiaoRequest(url, {
        method: "GET",
      });
    
      if (!Array.isArray(response)) {
        return [];
      }
    
      return response.map(sprint => SprintInfoSchema.parse(sprint));
    }
  • Zod input schema for list_sprints tool defining required organizationId and project id, optional status filter, page, and perPage parameters.
    export const ListSprintsSchema = z.object({
      organizationId: z.string().describe("Organization ID"),
      id: z.string().describe("Project unique identifier"),
      status: z.array(z.string()).optional().describe("Filter by status: TODO, DOING, ARCHIVED"),
      page: z.number().int().min(1).optional().describe("Page number"),
      perPage: z.number().int().min(1).max(100).optional().describe("Page size"),
    });
  • Tool registration entry defining the name, description, and input schema reference for the 'list_sprints' tool.
    {
      name: "list_sprints",
      description: "[Project Management] List sprints in a project",
      inputSchema: zodToJsonSchema(types.ListSprintsSchema),
    },
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions listing but does not specify whether this is a read-only operation, if it requires authentication, how pagination works (implied by parameters but not explained), or what the output format looks like. This leaves significant gaps in understanding the tool's behavior beyond basic listing.

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 concise with a single sentence plus a bracketed domain label, making it front-loaded and efficient. However, the bracketed '[Project Management]' adds minimal value and could be considered slightly redundant if the context is already clear from sibling tools. Overall, it avoids waste but lacks depth.

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 of a listing tool with 5 parameters, no annotations, and no output schema, the description is incomplete. It does not address behavioral aspects like pagination behavior, error handling, or return format, which are crucial for effective use. The high schema coverage helps, but the description fails to compensate for the lack of annotations and output details.

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%, with all parameters documented in the input schema (e.g., organizationId, id, status with filter values, page, perPage). The description does not add any additional meaning or context beyond what the schema provides, such as explaining relationships between parameters or usage examples. Baseline 3 is appropriate given the comprehensive schema coverage.

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 tool 'List sprints in a project', which clearly indicates the action (list) and resource (sprints). However, it does not differentiate from sibling tools like 'get_sprint' (singular) or specify scope beyond 'in a project', making it somewhat vague compared to alternatives. The bracketed '[Project Management]' adds domain context but doesn't enhance the core purpose.

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 explicit guidance is provided on when to use this tool versus alternatives such as 'get_sprint' (for a single sprint) or 'search_workitems' (which might include sprints). The description implies usage for listing sprints but offers no context about prerequisites, exclusions, or comparative scenarios with sibling tools.

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