Skip to main content
Glama
aliyun

AlibabaCloud DevOps MCP Server

Official
by aliyun

get_work_item

Retrieve work item details from Alibaba Cloud DevOps to access project information and track development tasks.

Instructions

[Project Management] Get information about a work item

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
organizationIdYesOrganization ID, can be found in the basic information page of the organization admin console
workItemIdYesWork item unique identifier, required parameter

Implementation Reference

  • MCP tool handler implementation for 'get_work_item': parses input arguments using GetWorkItemSchema, calls the helper function getWorkItemFunc, and formats the response as JSON text.
    case "get_work_item": {
      const args = types.GetWorkItemSchema.parse(request.params.arguments);
      const workItemInfo = await workitem.getWorkItemFunc(
        args.organizationId,
        args.workItemId
      );
      return {
        content: [{ type: "text", text: JSON.stringify(workItemInfo, null, 2) }],
      };
    }
  • Core helper function that performs the actual API call to retrieve work item details from the Yunxiao Projex API and parses the response using WorkItemSchema.
    export async function getWorkItemFunc(
      organizationId: string,
      workItemId: string
    ): Promise<z.infer<typeof WorkItemSchema>> {
      const url = `/oapi/v1/projex/organizations/${organizationId}/workitems/${workItemId}`;
    
      const response = await yunxiaoRequest(url, {
        method: "GET",
      });
    
      return WorkItemSchema.parse(response);
    }
  • Zod input schema definition (GetWorkItemSchema) used for validating tool arguments: organizationId and workItemId.
    export const GetWorkItemSchema = z.object({
      organizationId: z.string().describe("Organization ID, can be found in the basic information page of the organization admin console"),
      workItemId: z.string().describe("Work item unique identifier, required parameter"),
    });
  • Tool registration entry defining the tool name 'get_work_item', description, and input schema for MCP tool registry.
      name: "get_work_item",
      description: "[Project Management] Get information about a work item",
      inputSchema: zodToJsonSchema(types.GetWorkItemSchema),
    },
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 mentions 'Get information' but does not disclose behavioral traits such as whether it's read-only, requires authentication, has rate limits, or what the output format might be. This is a significant gap for a tool with no 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.

Conciseness4/5

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

The description is brief and front-loaded with the essential action, consisting of a single sentence. It avoids unnecessary words, though it could be more structured by explicitly stating the tool's scope or limitations.

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 lack of annotations and output schema, the description is incomplete. It does not explain what information is returned, potential errors, or how it fits into the broader toolset (e.g., vs. 'search_workitems'). For a read operation with no structured output documentation, more context is needed.

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 clear descriptions for both parameters in the input schema. The description does not add any additional meaning beyond the schema, such as explaining parameter relationships or usage examples, so it meets the baseline of 3 without compensating further.

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's purpose ('Get information about a work item') with a domain context hint ('[Project Management]'), which is clear but vague. It specifies the verb ('Get') and resource ('work item'), but lacks detail on what information is retrieved or how it differs from similar tools like 'search_workitems' or 'get_work_item_type'.

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. With sibling tools like 'search_workitems' (for searching) and 'get_work_item_type' (for metadata), the description does not indicate that this tool is for retrieving a specific work item by ID, leaving usage context implied rather than explicit.

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