Skip to main content
Glama
aliyun

AlibabaCloud DevOps MCP Server

Official
by aliyun

update_estimated_effort

Update estimated work hours for tasks in Alibaba Cloud DevOps projects to maintain accurate project planning and resource allocation.

Instructions

[Project Management] 更新登记预计工时

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
organizationIdYesorganizationId
workitemIdYes工作项唯一标识
idYes预计工时记录唯一标识
descriptionNo工作描述
operatorIdNo操作者的useId,个人token时该参数无效
ownerYes负责人,填userId
spentTimeYes预计工时
workTypeNo工作类别

Implementation Reference

  • MCP tool handler switch case that parses input arguments using the schema and delegates to the underlying updateEstimatedEffort function from operations/projex/effort.ts, returning a success message.
    case "update_estimated_effort": {
      const args = types.UpdateEstimatedEffortSchema.parse(request.params.arguments);
      await effort.updateEstimatedEffort({
        organizationId: args.organizationId,
        workitemId: args.workitemId,
        id: args.id,
        description: args.description,
        operatorId: args.operatorId,
        owner: args.owner,
        spentTime: args.spentTime,
        workType: args.workType
      });
      return {
        content: [{ type: "text", text: "Estimated effort updated successfully" }],
      };
    }
  • Zod schema defining the input parameters for the update_estimated_effort tool, including organizationId, workitemId, id, description, operatorId, owner, spentTime, and workType.
    export const UpdateEstimatedEffortSchema = z.object({
      organizationId: z.string().describe("organizationId"),
      workitemId: z.string().describe("工作项唯一标识"),
      id: z.string().describe("预计工时记录唯一标识"),
      description: z.string().max(500).optional().describe("工作描述"),
      operatorId: z.string().optional().describe("操作者的useId,个人token时该参数无效"),
      owner: z.string().describe("负责人,填userId"),
      spentTime: z.number().positive().describe("预计工时"),
      workType: z.string().optional().describe("工作类别"),
    });
  • Registration of the update_estimated_effort tool in the getEffortTools array, specifying name, description, and input schema.
    {
      name: "update_estimated_effort",
      description: "[Project Management] 更新登记预计工时",
      inputSchema: zodToJsonSchema(UpdateEstimatedEffortSchema),
    }
  • The core helper function that performs the actual API update by constructing the URL and sending a PUT request via yunxiaoRequest to the projex estimatedEfforts endpoint.
    export async function updateEstimatedEffort(
      params: z.infer<typeof CreateEstimatedEffortRequestSchema> & {
        organizationId: string;
        workitemId: string;
        id: string;
      }
    ) {
      const validatedParams = CreateEstimatedEffortRequestSchema.parse({
        description: params.description,
        operatorId: params.operatorId,
        owner: params.owner,
        spentTime: params.spentTime,
        workType: params.workType
      });
      
      const url = `/oapi/v1/projex/organizations/${params.organizationId}/workitems/${params.workitemId}/estimatedEfforts/${params.id}`;
      
      const response = await yunxiaoRequest(url, {
        method: "PUT",
        body: validatedParams
      });
    
      return response;
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. '更新登记' (update registration) implies a mutation operation, but the description doesn't specify what permissions are required, whether the update is reversible, what happens to existing data, or what the response looks like. For a mutation tool with 8 parameters and no annotation coverage, this is insufficient.

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 that gets straight to the point. There's no wasted language, though it could benefit from being slightly more informative given the tool's complexity. The bracketed '[Project Management]' context is helpful front-loading.

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 mutation tool with 8 parameters, 5 required fields, no annotations, and no output schema, the description is inadequate. It doesn't explain what happens after the update, what validation occurs, or how this tool differs from similar operations. The agent would need to guess about behavioral aspects and usage context.

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 8 parameters with basic descriptions. The tool description adds no additional parameter semantics beyond what's in the schema. The baseline of 3 is appropriate when the schema does the heavy lifting, though the description could have provided context about how parameters relate to each other.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('更新登记' meaning 'update registration') and resource ('预计工时' meaning 'estimated effort') in a project management context. It's specific about what gets updated (estimated effort records), though it doesn't explicitly differentiate from sibling tools like 'update_effort_record' or 'create_estimated_effort'.

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 like 'create_estimated_effort' or 'update_effort_record'. There's no mention of prerequisites, conditions, or typical scenarios for updating estimated effort versus creating new records or updating actual effort records.

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