Skip to main content
Glama
aliyun

Alibaba Cloud DMS MCP Server

Official
by aliyun

submitOrderApproval

Submit a DMS order for approval using its order ID to initiate the review process.

Instructions

Submit the order for approval in DMS using the order ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
order_idYesDMS order ID

Implementation Reference

  • The main handler function that calls the Alibaba Cloud DMS Enterprise client to submit an order for approval.
    async def submit_order_approval(
            order_id: str = Field(description="DMS order ID")
    ) -> Dict[str, Any]:
        client = create_client()
        req = dms_enterprise_20181101_models.SubmitOrderApprovalRequest()
        req.order_id = order_id
        try:
            resp = client.submit_order_approval(req)
            return resp.body.to_map()
        except Exception as e:
            logger.error(f"Error in submit_order_approval: {e}")
            raise
  • Tool registration in the configured database toolset.
    self.mcp.tool(name="submitOrderApproval",
                  description="Submit the order for approval in DMS using the order ID.",
                  annotations={"title": "提交工单审批", "readOnlyHint": False})(submit_order_approval)
  • Tool registration in the full toolset.
    self.mcp.tool(name="submitOrderApproval",
                  description="Submit the order for approval in DMS using the order ID.",
                  annotations={"title": "提交工单审批", "readOnlyHint": False})(submit_order_approval)
Behavior3/5

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

Annotations indicate readOnlyHint=false, implying a write operation, which aligns with 'submit' in the description. The description adds context by specifying the system ('DMS') and the required identifier ('order ID'), but lacks details on behavioral traits like approval workflow steps, permissions needed, or potential side effects (e.g., notifications sent). With annotations covering the safety profile, this is adequate but not rich.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

The description is a single, direct sentence that efficiently conveys the core action and resource without unnecessary words. It is front-loaded and wastes no space, making it highly concise and well-structured for quick understanding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity (a write operation with one parameter), no output schema, and annotations that cover basic safety (readOnlyHint=false), the description is minimally complete. It states what the tool does but lacks details on outcomes (e.g., what happens after submission) or error conditions, leaving gaps that could hinder effective use by an agent.

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?

The input schema has 100% coverage, fully documenting the 'order_id' parameter with a clear description. The description adds no additional meaning beyond implying the ID is used to locate the order, so it meets the baseline of 3 where the schema handles the heavy lifting without extra value from the description.

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 ('submit for approval') and the resource ('order in DMS'), making the purpose understandable. However, it doesn't explicitly differentiate this tool from potential siblings like 'createDataChangeOrder' or 'getOrderInfo', which would require a more specific scope or context to achieve a perfect score.

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. It doesn't mention prerequisites (e.g., order must be in a draft state), exclusions, or compare it to sibling tools like 'createDataChangeOrder' (which might create orders) or 'getOrderInfo' (which retrieves order details), leaving the agent with minimal context for selection.

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-dms-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server