Store Query

MUST DO

• Before starting, confirm that

  climbing-go

  is installed and can be executed directly in the current terminal
• All queries must be completed via the

  climbing-go

  command; do not bypass the CLI to directly request MCP
• Only use real fields and store IDs returned by the command; do not guess or fabricate data
• When the user uses natural language, first categorize the question as "query store list" or "query store details", then select the corresponding command
• If the user asks questions like "what time does it open", "what time does it close", "where is the address", "what's the phone number", first narrow down the scope with

  store list

  , then use

  store get

  to view details

Scope

• Supports

  store list

• Supports

  store get

• Does not support courses, memberships, orders, private stores, or other unopened data

Typical User Phrases

• Find a climbing gym
• Find a climbing gym
• Go climbing
• Where to climb in Shenzhen
• Where are the climbing gyms in Shanghai
• Beijing climbing gyms
• Where is Banana Climbing
• What time does Banana Climbing open in Shenzhen
• What's the address of this store
• What are the opening hours

• find a climbing gym

• where can I climb in Shanghai

• bouldering gym in Shenzhen

• what time does it open

• what are the opening hours

Setup

climbing-go --help

npm install -g climbing-go

pnpm exec tsx src/index.ts --help

Commands

climbing-go store list
climbing-go store list --city 上海 --search 香蕉
climbing-go store list --city 上海 --search 香蕉 --limit 10
climbing-go store get store_123

store list

--limit

--offset

Query Strategy

1. If the user is just looking for a store, such as "find a climbing gym", "go climbing", "where to climb", prioritize using

   store list

2. If the user mentions a city, such as "Shenzhen", "Shanghai", "where to climb in Beijing", add the

   --city

   parameter
3. If the user mentions a store name or keyword, such as "Banana Climbing", add the

   --search

   parameter when querying the list
4. If the user asks for details such as address, phone number, opening hours, or what time it opens, first find the candidate stores, then use

   store get <storeId>

5. If there are multiple possible matches in the list results, return the real candidates for the user to confirm; do not guess the specific store on your own

Query Examples

• Find a climbing gym

  ->

  climbing-go store list

• Where to climb in Shenzhen

  ->

  climbing-go store list --city 深圳

• Banana Climbing in Shanghai

  ->

  climbing-go store list --city 上海 --search 香蕉 --limit 10

• What time does Banana Climbing open in Shenzhen

  -> First run

  climbing-go store list --city 深圳 --search 香蕉 --limit 10

  , then

  climbing-go store get <storeId>

• find a climbing gym in Beijing

  ->

  climbing-go store list --city 北京

• what time does Banana climb open in Shenzhen

  -> First run

  climbing-go store list --city 深圳 --search 香蕉 --limit 10

  , then

  climbing-go store get <storeId>

Output

• store list

  returns JSON; focus on

  data.stores

  and

  data.count

• store get

  returns JSON; focus on

  data.store

• A successful response includes

  ok

  ,

  tool

  ,

  endpoint

  , and

  data

• When answering questions like "what time does it open", only reference the real opening hours field in

  data.store

  ; if it is not present in the response, clearly state that the current public data does not provide it

Failure Handling

• When

  not_found

  is returned, it means the store ID does not exist or is not within the public scope
• When

  endpoint_not_found

  ,

  timeout

  , or

  network_error

  is returned, directly report the real error; do not guess store data