Skip to main content
Glama
aliyun

AlibabaCloud DevOps MCP Server

Official
by aliyun

list_estimated_efforts

Retrieve detailed estimated work hours for specific tasks in Alibaba Cloud DevOps projects to support planning and resource allocation.

Instructions

[Project Management] 获取预计工时明细

Input Schema

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

Implementation Reference

  • MCP tool handler implementation for 'list_estimated_efforts'. Parses input arguments using the schema, calls the underlying effort service function, and formats the response as JSON text.
    case "list_estimated_efforts": {
      const args = types.ListEstimatedEffortsSchema.parse(request.params.arguments);
      const estimatedEfforts = await effort.listEstimatedEfforts({
        id: args.id,
        organizationId: args.organizationId
      });
      return {
        content: [{ type: "text", text: JSON.stringify(estimatedEfforts, null, 2) }],
      };
    }
  • Core helper function that performs the API request to fetch estimated efforts for a workitem and parses the response using Zod.
    export async function listEstimatedEfforts(
      params: z.infer<typeof ListEstimatedEffortsSchema>
    ) {
      const validatedParams = ListEstimatedEffortsSchema.parse(params);
      
      const url = `/oapi/v1/projex/organizations/${validatedParams.organizationId}/workitems/${validatedParams.id}/estimatedEfforts`;
      
      const response = await yunxiaoRequest(url, {
        method: "GET"
      });
    
      return z.array(EstimatedEffortSchema).parse(response);
    }
  • Tool registration in the effort tools array, including name, description, and input schema converted to JSON schema.
      name: "list_estimated_efforts",
      description: "[Project Management] 获取预计工时明细",
      inputSchema: zodToJsonSchema(ListEstimatedEffortsSchema),
    },
  • Zod schema definition for input parameters: workitem id and organizationId.
    export const ListEstimatedEffortsSchema = 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?

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description only states it 'gets estimated effort details' without specifying whether this is a read-only operation, what permissions are required, how results are formatted, or any limitations (e.g., pagination, rate limits). This leaves significant gaps for a tool that likely queries data.

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 phrase, which is efficient and front-loaded. However, it's arguably too brief, as it omits necessary details like the resource type, making it slightly under-specified rather than optimally concise.

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 doesn't explain what 'estimated effort details' include, how results are returned, or any behavioral traits. For a tool with two required parameters and no structured output information, more context is needed to guide effective use.

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 both parameters ('id' and 'organizationId') documented in the schema. The description doesn't add any additional meaning about the parameters beyond what's in the schema (e.g., it doesn't clarify what 'id' refers to or provide examples). Given the high schema coverage, a baseline score of 3 is appropriate.

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 '[Project Management] 获取预计工时明细' states the domain (Project Management) and the action (获取预计工时明细 - get estimated effort details), which clarifies the purpose. However, it doesn't specify what resource this applies to (work items, projects, etc.) or differentiate it from sibling tools like 'list_effort_records' or 'list_current_user_effort_records', making it somewhat 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?

The description provides no guidance on when to use this tool versus alternatives. There are several sibling tools related to efforts (list_effort_records, list_current_user_effort_records, create_estimated_effort, update_estimated_effort), but the description doesn't indicate how this tool differs from them or specify any prerequisites or context 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