Gold Dust Lab · Infrastructure
How a question travels from you to the shop’s data — and the one place the local qwen model does the thinking instead of Claude.
Every request runs left to right — and only after a Cisco Duo sign-in. Just one branch drops down to the local model.
/mcp call needs a valid Cisco Duo JWT.
Dashed = your AWS box; the shop’s data lives inside the MCP server.
Talk to the shop in plain language — these are the calls that run behind the scenes.
| # | Tool | Ask it something like… |
|---|---|---|
| 1 | get_company_info | “What does Gold Dust Lab sell, and when are you open?” |
| 2 | search_products | “What Fender guitars do you have?” |
| 3 | get_product | “Tell me about GDL-R001 — Dark Side of the Moon.” |
| 4 | search_knowledge_base | “What’s your return policy for records?” |
| 5 | get_order | “What’s the status of order GDL-1042?” |
| 6 | list_customer_orders | “What has alice.turner@example.com ordered?” |
| 7 | create_support_ticket | “Open a ticket for bob.keeler@example.com — buzzing fret.” |
| 8 | request_quote | “Quote me a Stratocaster and two Dark Side of the Moon.” |
| 9 | list_tickets | “Does bob.keeler@example.com have any open tickets?” |
| 10 | get_ticket | “What’s in ticket GDL-T5001?” |
| 11 | get_quote | “Show me quote GDL-Q9005.” |
| 12 | ask_gold_dust_lab | “Ask the local assistant: when did order GDL-1042 ship?”runs qwen |
The local model only takes over on one path. Everywhere else, Claude is the brain and the tools just hand back data.
| What you do | Who does the thinking | qwen? |
|---|---|---|
| Ask Claude chat / Claude Code anything → it uses tools 1–8 | Claude — in the cloud | NO |
Call tool 9, ask_gold_dust_lab | qwen2.5:3b — on your AWS box | YES |
Rule of thumb: qwen only runs through ask_gold_dust_lab —
which keeps the reasoning and data on your box. Anything else is answered by Claude.