> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tagada.io/llms.txt
> Use this file to discover all available pages before exploring further.
# Prompt Library
> Three ready-to-use prompts for the Tagada Config MCP.
Open one, copy it, replace the placeholders. Each prompt carries the order the checks should run in — which is rarely the order you would guess.
```text theme={null}
You have access to the Tagada Config MCP. Diagnose this store.
Store:
Symptom:
Work in this order:
1. Call list_stores and match the store by name. Never guess a store id.
2. Pick the first check from the symptom:
- No orders at all, or a sudden stop -> check_checkout. A store taking
zero orders is almost always unreachable (no active funnel, an
unpublished one, or an unverified domain), not a payment problem.
- Cards declined, payments failing -> check_payment.
- Complaints from one country -> check_shipping.
- One product cannot be bought -> check_catalog.
- Unclear -> check_checkout, then check_payment.
3. Run the remaining checks anyway. A second blocker is common and the first
one hides it.
4. Call get_setup_status last, and point out every step the checklist calls
"completed" that a check contradicts.
Report all ERROR findings before any WARNING. For each one give the message,
the evidence, and where in the CRM I fix it. If a check fails because of my
permissions, say so instead of guessing.
```
```text theme={null}
You have access to the Tagada Config MCP. Run a pre-launch check on this
store and give me a go / no-go.
Store:
Launching in:
Selling in:
1. Call list_stores and match the store by name. Never guess a store id.
2. Run all four checks - check_catalog, check_shipping, check_payment,
check_checkout. Run all four even if the first one fails.
3. Call get_setup_status and note any step it calls "completed" that a check
contradicts.
Then answer in this order:
- VERDICT: GO or NO-GO.
- BLOCKERS: every ERROR, one line each, with the CRM screen to fix it.
- RISKS: every WARNING, one line each.
- NOT VERIFIED: anything you could not check, and why.
Confirm explicitly that the catalog is priced in , that shipping
covers , and that at least one processor can charge in .
A store can pass the checklist at 5/5 and still be unable to take an order.
```
```text theme={null}
You have access to the Tagada Config MCP. Audit every store I can reach.
1. Call list_stores. It spans every organisation I belong to - cover all of
them, not just the first.
2. For each store, run check_checkout and check_payment. Those two decide
whether an order can be placed at all.
3. For any store failing either one, also run check_catalog and
check_shipping to get the full picture.
Give me a single table:
Store | Organisation | Can take orders? | Blockers
Broken stores first. One short line per blocker, no evidence dumps.
End with the stores you could not check and why. A missing permission is a
result, not a store to leave out.
```
## Next
The nine tools, what they report, and the one that writes.
Connect your client.