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

智能发单-订单询价

Get instant delivery price quotes for UU跑腿 orders by entering pickup and destination addresses to estimate costs before booking.

Instructions

查询订单价格,需要需要输入开始地址,结束地址。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
from_addressYes开始地址,要求完整地址信息。必要字段
to_addressYes结束地址,要求完整地址信息,必要字段
city_nameYes配送城市名字,如果没有带’市‘,需要补充,比如郑州市,不能只是郑州,非必填

Implementation Reference

  • The implementation of the '智能发单-订单询价' tool, which accepts order addresses and city name and calls the order pricing API.
    @mcp.tool(name="智能发单-订单询价", description="查询订单价格,需要需要输入开始地址,结束地址。")
    async def order_price(from_address: str = Field(description="开始地址,要求完整地址信息。必要字段"),  # 开始地址,例如:阳光城5号楼6层6号
                          to_address: str = Field(description="结束地址,要求完整地址信息,必要字段"),  # 结束地址,例如:楷林国际4层210号
                          city_name: str = Field(
                              description="配送城市名字,如果没有带’市‘,需要补充,比如郑州市,不能只是郑州,非必填"), ) -> dict:
        if ORDER_CITY:
            city_name = ORDER_CITY
        biz = {
            'fromAddress': from_address,
            'toAddress': to_address,
            'sendType': "SEND",
            'cityName': city_name,
            'specialChannel': 1
        }
        url = f"{OPENAPI_URL_BASE}order/orderPrice"
        return post_send(biz, url)
Behavior2/5

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

With no annotations provided, the description carries full burden but discloses nothing about side effects (whether this creates a temporary quote ID), idempotency, rate limits, or response format. Only input requirements are mentioned.

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 is appropriately front-loaded (purpose first), though marred by a typo ('需要需要'). No structural waste, but the typo slightly undermines professionalism.

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?

Lacks output schema coverage, so description should explain return values (price structure, validity period). Also fails to mention the required city_name parameter, leaving the description incomplete for the 3-parameter tool.

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. The description mentions start/end addresses but entirely omits the required 'city_name' parameter, adding no additional syntax guidance beyond what the schema already provides.

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 states the core function ('查询订单价格') with specific verb and resource, but fails to distinguish from sibling '智能发单-创建订单' (e.g., clarifying this is a pre-creation price check vs. actual booking).

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?

No guidance on when to use this tool versus alternatives. Missing critical workflow context that this should be called before '创建订单' to determine pricing, or when to skip it.

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