Skip to main content
Glama
Sign In
luckin-mcp-proxy

luckin-mcp-proxy

by wyhAcc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

orderStatus

Check the status of a coffee order, including the pickup code and preparation progress. If no order ID is provided, retrieves the most recent order.

Instructions

查询订单状态（取餐码、制作进度）。orderId 缺省时查最近一单。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "orderStatus"
  }
}

Input Schema

NameRequiredDescriptionDefault
orderIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries full burden. It discloses the default behavior and the information returned (status, pickup code, progress), but lacks details on side effects, authentication needs, or rate limits.

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 concise with two sentences, front-loading the purpose and then addressing the parameter default. Every sentence is necessary and no redundancy.

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

Completeness4/5

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

Given the tool has one optional parameter and no output schema, the description covers the primary behavior, default logic, and output content. Missing details like error handling or authentication are minor gaps.

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?

The schema has 0% description coverage, so the description must compensate. It does by explaining that orderId is optional and that omitting it queries the most recent order, adding meaningful context beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool queries order status including pickup code and preparation progress. It distinguishes from sibling tools like cancelOrder and confirmOrder by focusing on status retrieval only.

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?

The description implies usage for checking order status and mentions default behavior when orderId is omitted, but does not provide explicit guidance on when to use this tool versus alternatives like searchProduct or reorder.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools