luckin-mcp-proxy

Overview Schema Source Related Servers Discussions Admin

preferences

View or set coffee preferences including default shop, temperature, sugar level, and cup size. Also check recent orders and frequently ordered items.

Instructions

查看或设置偏好：常用门店、默认口味（冰/热、糖度、杯型），并可查看最近订单与常点商品。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "preferences"
  }
}

Input Schema

Name	Required	Description	Default
`action`	Yes
`defaultShopName`	No
`temperature`	No
`sugar`	No
`cupSize`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 10, 2026

TDQS

A3.5/5.0

Behavior3/5

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

No annotations are provided, so the description must fully disclose behavior. It reveals that the tool supports both read and write operations, but lacks details on side effects (e.g., whether writing is immediate, persistent) or what the 'get' action returns. The description adds context beyond the schema but is not exhaustive.

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?

The description is a single sentence, concise and front-loaded with the verb phrase. It efficiently conveys the main functionality without redundancy, though it could be slightly more structured.

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?

Given no output schema and no parameter descriptions in the schema, the description does not fully explain expected outputs or parameter details. The mention of 'recent orders' and 'frequent items' without schema mapping leaves gaps in understanding, especially for new agents.

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 description coverage is 0%, so the description must compensate. It explains the domain of parameters (e.g., 'temperature' as icy/hot, 'sugar' as sweetness) and the 'action' enum. However, it mentions 'recent orders' and 'frequent items' which do not correspond to any schema parameter or output field, causing ambiguity.

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's purpose: viewing or setting preferences (frequently used store, default temperature, sugar level, cup size) and viewing recent orders and frequently ordered items. It uses specific verbs and resources, distinguishing it from sibling tools focused on order management.

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 preference management but does not explicitly state when to use this tool versus alternatives like 'quickOrder' or 'orderStatus'. No when-not-to-use guidance is provided.

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

Deploy Server