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

luckin-mcp-proxy

by wyhAcc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

findShop

Search for Luckin Coffee stores by name. Provide your location on first use, then the tool recalls your frequent store coordinates.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
longitudeNo
latitudeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

The description discloses key behavioral traits: the tool is stateful, memorizing coordinates after first use. This is valuable as no annotations are provided. However, it does not mention authentication needs, rate limits, or what happens if coordinates are not provided on first use.

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 concise with two clauses in one sentence, front-loading the purpose. Every word adds value. It could be slightly more structured, but it is efficient.

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?

Given 3 parameters, no output schema, and no annotations, the description covers usage and stateful behavior. However, it lacks information about the return format (e.g., list of stores with details), which is a gap in completeness.

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?

With 0% schema coverage, the description adds meaning to the parameters: name for searching, longitude/latitude for initial use. However, it does not specify coordinate format (e.g., decimal degrees) or explain how 'memorized common store coordinates' work, leaving ambiguity. Baseline 3 is appropriate as some value is added but gaps remain.

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 stores by name ('按名称搜索瑞幸门店'), which is a specific verb+resource. It distinguishes from sibling tools like searchProduct (search products) and other order-related tools.

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

Usage Guidelines4/5

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

The description provides explicit usage context: first use requires coordinates ('首次使用需提供经纬度'), and subsequent uses rely on memorized coordinates ('之后用记忆的常用门店坐标'). This guides the agent on when to provide longitude/latitude. However, it does not explicitly state when not to use this tool or suggest alternatives.

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