Skip to main content
Glama
uupt-mcp
by uupt-mcp

智能发单-取消订单

Cancel delivery orders on UU跑腿 by providing order code and cancellation reason to manage order status changes.

Instructions

取消订单,需要需要输入订单编号

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
order_codeYes订单编号order_code
reasonYes取消原因reason,例如:不想取了

Implementation Reference

  • Implementation of the "智能发单-取消订单" tool handler using order_cancel function.
    @mcp.tool(name="智能发单-取消订单", description="取消订单,需要需要输入订单编号")
    async def order_cancel(order_code: str = Field(description="订单编号order_code"),
                           reason: str = Field(description="取消原因reason,例如:不想取了"),
                           ) -> dict:
        biz = {
            'order_code': order_code,
            'reason': reason
        }
        url = f"{OPENAPI_URL_BASE}order/cancelOrder"
        return post_send(biz, url)
Behavior2/5

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

No annotations provided, so description carries full burden. While '取消' implies a write/mutation operation, the description fails to disclose consequences (refunds, fees), reversibility, or state transitions. No mention of rate limits or authorization requirements.

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?

Single sentence structure with action front-loaded. Appropriately brief for the tool complexity, though contains a typo ('需要需要'). No wasted words otherwise.

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?

Adequate for a 2-parameter tool but missing lifecycle context crucial for cancellations (e.g., 'can only cancel pending orders'). Does not compensate for lack of output schema with explanation of return values or side effects.

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 coverage is 100%, establishing baseline 3. Description mentions order_code but entirely omits the required 'reason' parameter. Adds no semantic context beyond schema (e.g., no format details, constraints, or examples beyond what's in schema).

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?

States specific verb (取消/cancel) and resource (订单/order) clearly. However, lacks explicit differentiation from siblings (e.g., when to cancel vs. when to create or query), though the action itself is unambiguous.

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?

Provides minimal guidance - only mentions that order_code is required. Contains no information about when cancellation is appropriate (e.g., order states), timing restrictions, or prerequisites. No 'when-not' guidance provided.

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/uupt-mcp/uupt-mcp-server'

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