Skip to main content
Glama
aliyun

AlibabaCloud DevOps MCP Server

Official
by aliyun

get_sprint

Retrieve sprint details from Alibaba Cloud DevOps projects to track progress and manage development cycles.

Instructions

[Project Management] Get information about a sprint

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
organizationIdYesOrganization ID
projectIdYesProject unique identifier
idYesSprint unique identifier

Implementation Reference

  • Handler for 'get_sprint' tool: parses input arguments using GetSprintSchema, calls sprint.getSprintFunc, and returns JSON stringified sprint info.
    case "get_sprint": {
      const args = types.GetSprintSchema.parse(request.params.arguments);
      const sprintInfo = await sprint.getSprintFunc(
        args.organizationId,
        args.projectId,
        args.id
      );
      return {
        content: [{ type: "text", text: JSON.stringify(sprintInfo, null, 2) }],
      };
    }
  • Input schema (GetSprintSchema) for validating arguments: organizationId, projectId, sprint id.
    export const GetSprintSchema = z.object({
      organizationId: z.string().describe("Organization ID"),
      projectId: z.string().describe("Project unique identifier"),
      id: z.string().describe("Sprint unique identifier"),
    });
  • Tool registration: defines name 'get_sprint', description, and input schema from GetSprintSchema.
      name: "get_sprint",
      description: "[Project Management] Get information about a sprint",
      inputSchema: zodToJsonSchema(types.GetSprintSchema),
    },
  • Core implementation (getSprintFunc): makes GET request to Yunxiao API to fetch sprint info and parses with SprintInfoSchema.
    export async function getSprintFunc(
      organizationId: string,
      projectId: string,
      id: string
    ): Promise<z.infer<typeof SprintInfoSchema>> {
      const url = `/oapi/v1/projex/organizations/${organizationId}/projects/${projectId}/sprints/${id}`;
    
      const response = await yunxiaoRequest(url, {
        method: "GET",
      });
    
      return SprintInfoSchema.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 only states it 'gets information' without specifying what information is returned, whether it requires specific permissions, if there are rate limits, or how errors are handled. This is inadequate for a tool with 3 required parameters and no output schema.

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 extremely concise with just one sentence, but it's appropriately sized for a simple retrieval tool. The bracketed '[Project Management]' context is front-loaded, though the single sentence could be more informative without sacrificing brevity.

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 tool with 3 required parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain what information is returned, the format of the response, or any behavioral characteristics. The context signals indicate this is a non-trivial tool that needs more complete documentation.

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 three parameters (organizationId, projectId, id). The description adds no additional meaning about these parameters beyond what's in the schema, maintaining the baseline score for high 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 'Get information about a sprint' which provides a basic verb+resource combination, but it's vague about what specific information is retrieved. It distinguishes from siblings like 'create_sprint' and 'update_sprint' by being a read operation, but doesn't clearly differentiate from 'list_sprints' which might provide similar information in a different format.

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 about when to use this tool versus alternatives. The description doesn't mention when to choose 'get_sprint' over 'list_sprints' or other related tools, nor does it specify prerequisites or appropriate contexts for its use.

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