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

luckin-mcp-proxy

by wyhAcc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

searchProduct

Search for Luckin coffee products by name or query, returning product details including price, SKU, and attributes. Supports specifying a store location for localized results.

Instructions

搜索瑞幸商品（自动重试不稳定的上游搜索），返回名称/价格/SKU/属性。

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": {
      "query": "<query>"
    },
    "name": "searchProduct"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes
shopNameNo门店名，缺省用常用门店

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations provided, the description discloses retry logic for unstable upstream searches and specifies the output fields. This provides useful behavioral context beyond the schema, though additional details like auth requirements or side effects are absent.

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 a single, front-loaded sentence containing the action, retry detail, and output spec. Every element is essential and clearly communicated.

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?

For a search tool with two parameters and no output schema, the description covers purpose, retry behavior, and output fields. It lacks guidance on when to use versus sibling tools and does not mention pagination or error conditions, but otherwise is sufficient.

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 50% (one parameter described in schema). The description does not add meaning to the 'query' parameter, but its purpose is clear from the context. The 'shopName' parameter is already described in the schema. The description compensates minimally by implying the nature of the query.

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 searches for Luckin products and lists the specific fields returned (name/price/SKU/attributes). It also mentions retry behavior, which adds precision. This distinguishes it from sibling tools like findShop (shop search) and others.

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?

There is no explicit guidance on when to use this tool versus alternatives. The description implies it is for product search, but does not mention when not to use it or contrast it with siblings like quickOrder 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