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

智能发单-创建订单

Create delivery orders through UU跑腿 by providing a price token and recipient phone number to finalize and submit order requests.

Instructions

自动创建订单,需要需要输入:计算订单价格接口返回的price_token,必传字段,收件人电话:receiver_phone,必传字段

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
price_tokenYes计算订单价格接口返回的price_token,必填字段
receiver_phoneYes收件人电话,例如:15288888888,必填字段

Implementation Reference

  • The implementation of the tool '智能发单-创建订单', which takes a price_token and receiver_phone to create an order using the UUPT OpenAPI.
    @mcp.tool(name="智能发单-创建订单",
              description="自动创建订单,需要需要输入:计算订单价格接口返回的price_token,必传字段,收件人电话:receiver_phone,必传字段")
    async def order_create(price_token: str = Field(description="计算订单价格接口返回的price_token,必填字段"),
                           receiver_phone: str = Field(description="收件人电话,例如:15288888888,必填字段"),
                           ) -> dict:
        biz = {
            'priceToken': price_token,
            'receiver_phone': receiver_phone,
            'pushType': "OPEN_ORDER",
            'payType': "BALANCE_PAY",
            'specialChannel': 1,
            'specialType': "NOT_NEED_WARM"
        }
        url = f"{OPENAPI_URL_BASE}order/addOrder"
        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. States 'automatic' creation but fails to disclose critical behavioral traits: whether this creates a binding financial commitment, if it's reversible (cancel order sibling exists), rate limits, or what success/failure looks like. For a transactional mutation tool, this is a significant gap.

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

Conciseness2/5

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

Contains grammatical error ('需要需要' - repeated word). Structure is run-on with poor punctuation usage. Information is front-loaded but parameter listing is awkward. Not efficiently structured despite being short.

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?

For a 2-parameter creation tool with no output schema, the description covers the prerequisite workflow (price calculation) but omits what the tool returns (likely order ID/details) and lacks safety warnings appropriate for order creation operations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema coverage, baseline is 3. The description adds valuable workflow context that price_token must come from the price calculation interface, which aids parameter understanding beyond the schema's type information.

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 '自动创建订单' (automatically create order) which clearly identifies the action and resource. Mentions the price_token prerequisite which implicitly distinguishes this from the sibling '订单询价' (price inquiry) tool, though it could explicitly name that tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implies workflow sequence by noting price_token must come from the price calculation interface, but lacks explicit when-to-use guidance (e.g., 'Use this after getting a price quote') or exclusions (e.g., 'Do not use if price is not confirmed').

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