Skip to main content
Glama
aliyun

AlibabaCloud DevOps MCP Server

Official
by aliyun

list_effort_records

Retrieve detailed actual effort records for work items to track time spent on tasks in Alibaba Cloud DevOps projects.

Instructions

[Project Management] 获取实际工时明细

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes工作项唯一标识
organizationIdYesorganizationId

Implementation Reference

  • MCP tool handler switch case that parses input arguments using ListEffortRecordsSchema, calls the listEffortRecords helper function, and returns the effort records as a JSON-formatted text response.
    case "list_effort_records": {
      const args = types.ListEffortRecordsSchema.parse(request.params.arguments);
      const effortRecords = await effort.listEffortRecords({
        id: args.id,
        organizationId: args.organizationId
      });
      return {
        content: [{ type: "text", text: JSON.stringify(effortRecords, null, 2) }],
      };
    }
  • Tool registration in the getEffortTools array, defining the tool name, description, and input schema derived from ListEffortRecordsSchema.
    {
      name: "list_effort_records",
      description: "[Project Management] 获取实际工时明细",
      inputSchema: zodToJsonSchema(ListEffortRecordsSchema),
    },
  • Helper function implementing the core logic: validates parameters, constructs API URL for fetching effort records of a specific workitem, performs GET request using yunxiaoRequest, and parses response as array of EffortRecordSchema.
    export async function listEffortRecords(
      params: z.infer<typeof ListEffortRecordsSchema>
    ) {
      const validatedParams = ListEffortRecordsSchema.parse(params);
      
      const url = `/oapi/v1/projex/organizations/${validatedParams.organizationId}/workitems/${validatedParams.id}/effortRecords`;
      
      const response = await yunxiaoRequest(url, {
        method: "GET"
      });
    
      return z.array(EffortRecordSchema).parse(response);
    }
  • Zod schema definition for input parameters: workitem ID and organization ID.
    export const ListEffortRecordsSchema = z.object({
      id: z.string().describe("工作项唯一标识"),
      organizationId: z.string().describe("organizationId"),
    });
Behavior2/5

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

With no annotations, the description carries full burden but provides minimal behavioral insight. It implies a read operation ('获取' means get/fetch) but doesn't disclose permissions needed, rate limits, pagination, or what happens if parameters are invalid. For a tool with no annotations, this is inadequate transparency.

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 a single, efficient sentence in Chinese. It's front-loaded with the core purpose. However, it could be more structured by explicitly stating it's a list/query operation rather than just '获取' (get).

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 no annotations and no output schema, the description is insufficient. It doesn't explain what 'effort records' are, the return format, or behavioral constraints. Given the complexity implied by sibling tools (e.g., create/update effort records), more context is needed for the agent to use this 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 parameters are documented in the schema. The description adds no additional meaning about 'id' or 'organizationId' beyond what's in the schema ('工作项唯一标识' for id, no description for organizationId). Baseline 3 is appropriate when schema does the work.

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 '获取实际工时明细' (Get actual work time details) states a general purpose but lacks specificity. It doesn't clarify what 'effort records' are, what format the details come in, or how this differs from sibling tools like 'list_current_user_effort_records'. The purpose is understandable but 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?

No guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, context (e.g., project management workflow), or differentiate from similar tools like 'list_current_user_effort_records' or 'list_estimated_efforts'. The description provides no usage context.

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