CardShow

View saved version →

---
name: cardshow-catch-up-on-my-market
description: Brief a signed-in collector on saved upcoming shows, followed-shop and seller activity, current CardShow plans, and shop alert choices. Use when a user asks what changed, what is coming up, what they missed, what needs attention, or wants to follow one shop, save one show, or adjust CardShow shop alerts.
---

# Catch up on the collector's CardShow market

Summarize only the signed-in collector's current CardShow relationships and time-sensitive activity. Do not turn a chronological feed into noise.

## Build the briefing

1. Call `cardshow_get_my_alerts` for saved upcoming shows, followed activity, current shop alert choices, and the delivery notice.
2. Call `cardshow_get_my_planning` when private plans, saved or followed IDs, or next actions are relevant.
3. Group the result into:
   - saved shows approaching soon;
   - meaningful new shop or seller activity;
   - plans that still need preparation; and
   - alert choices that may not match the user's stated intent.
4. Prioritize by actual date and relevance. Do not promote the first returned record merely because of response order.
5. Distinguish public business activity from the collector's private saved, followed, plan, and alert state.

Do not expose location history, another collector's activity, push tokens, or delivery logs. Do not claim an alert was delivered. CardShow alert choices still depend on notification permission on the customer's device.

## Prepare one relationship change

When the user asks to follow a shop, save a show, or change alerts:

1. Resolve one exact shop or show with `search`, `fetch`, or a current CardShow read.
2. Refresh planning and alerts before previewing the change.
3. State the exact target and desired final state. Never use a blind toggle.
4. For alerts, list only the choices that will change and state that omitted choices will be preserved.
5. If the shop is not followed, preview the exact follow and alert effects together; apply the follow first, refresh alerts, then apply only the confirmed alert merge.

## Confirm and verify

Ask for explicit confirmation immediately before each listed final-state action. Then use only the matching tool:

- `cardshow_set_shop_follow`;
- `cardshow_set_saved_show`; or
- `cardshow_set_shop_alert_preferences`.

Re-read alerts or planning after the action and report the final state plus the device-permission limitation. Refuse bulk follow, save, attendance, or alert changes that bypass exact targets and confirmation.

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: cardshow-find-my-best-show
description: Compare upcoming CardShow events against a collector's dates, place, saved plans, seller-declared coverage, and optional connected HobbyWise Hunt List. Use when a user asks which card show to attend, wants events near a place or during a date range, asks where they are most likely to find their targets, or wants a transparent shortlist instead of a generic directory search.
---

# Find the best CardShow event

Recommend events from CardShow evidence and the collector's own priorities. Keep the ranking explainable and never turn seller declarations into inventory guarantees.

## Establish the search

1. Resolve the intended place and date range. State exact dates when the user uses relative language such as “this weekend.”
2. Ask a follow-up only when the missing place or date would materially change the result.
3. Use `cardshow_get_my_planning` when signed-in saves or existing plans are relevant.
4. Use `cardshow_find_events` for the bounded public candidate set.
5. When the customer has the required CardShow access and approved HobbyWise connection, use `cardshow_recommend_events_for_my_hunt_list` for the same place and dates.
6. If Hunt List access is unavailable, continue with public CardShow discovery and user-stated priorities. Do not infer or request private HobbyWise fields.

## Compare the evidence

- Use `cardshow_get_show_supply` for a selected event or a small set of serious candidates when the Hunt List recommendation did not already provide enough seller evidence.
- Separate exact seller-listed item matches, strong category matches, and general leads.
- Consider date and place fit, current saved/planned state, matched targets, declared category coverage, and how complete the seller information is.
- Do not invent distance, travel time, admission cost, vendor count, inventory, verification, or availability when CardShow did not return it.
- Do not rank an event first merely because it appears first in a tool result.

## Present the shortlist

Return a compact comparison with:

1. the best one to three events for the stated goal;
2. the evidence supporting each choice;
3. the important tradeoffs or missing information;
4. unmatched Hunt List targets when available; and
5. the CardShow notice that seller declarations are planning leads, not guarantees or reservations.

If no event has meaningful evidence, say so and show the best directory candidates without pretending they match.

## Save only after confirmation

Do not save, unsave, or change attendance during comparison. If the user asks to save or set attendance, refresh the exact show and current planning state, preview the exact final state, ask for explicit confirmation, use the matching final-state tool, and verify with a fresh read. Never apply a bulk action to multiple shows under vague confirmation.

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: cardshow-find-online-businesses
description: Search the full current directory of Online stores and breakers whose owners submitted and manage profiles through CardShow Pro and CardShow's in-app review process, inspect their selling profiles, and optionally save or remove one Pro-only private shortlist item after confirmation. MCP discovery does not submit, manage, approve, or publish business profiles. Use for online-business discovery, not physical shops, shows, purchases, or ownership approval.
---

# Find Online businesses in CardShow

Use `cardshow_browse_online_businesses` with the customer's collecting interests and supported filters. Search, combined filters, and profiles are available on Free and Pro; use the full current directory returned by CardShow. The directory contains only businesses that are currently eligible, whose owners submitted and manage profiles through CardShow Pro in the app, and passed review. CardShow controls current visibility server-side; do not infer a complete directory, visibility, or listing eligibility from collector Pro status. A collector's Pro subscription does not establish ownership or permission to list a business. This MCP workflow only discovers and reads businesses; it cannot submit, manage, approve, or publish business profiles. No editorial seed businesses are included. The private saved shortlist is Pro-only. A saved-only access error means access was denied, not that the shortlist is empty. Never describe a partial or unavailable response as the full directory.

Use returned exact IDs with `cardshow_get_online_business` to inspect a currently visible profile, its reviewed selling links, and source dates. Respect blocked and unavailable responses; do not retry anonymously, use a stale profile as fallback, or substitute another account. A visible directory listing does not prove the collector owns or may publish that business. Online identities have no map location or directions. Seller links and reviewed sources are leads, not guarantees of stock, authenticity, ownership, price, or availability. Do not contact the seller or make a purchase.

For a shortlist change, read the exact profile first. If a `shortlistReview` is available, state the business name, whether it is currently saved, and the requested final saved state. Ask for confirmation of that exact change. A request to find or compare businesses does not authorize saving them. After confirmation, call `cardshow_set_online_business_saved` with the unchanged review, desired `saved` value, and `confirmed: true`. This changes only the signed-in customer's private shortlist. Never fabricate a review, account reference, or business ID.

If the account changes, the review expires, or the profile changes, read and confirm again. On an uncertain transport result, retry only the same confirmed desired state while the review is valid; never toggle or infer success from a failed call. Report success only from a successful tool result. Ownership claims, business edits, reporting, blocks, and publication remain in the existing CardShow app workflows.

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: cardshow-prepare-show-day
description: Build and optionally apply a practical private plan for one exact CardShow event. Use when a user asks for a show-day brief, checklist, seller stops, target plan, packing reminders, an event game plan, or help marking checklist items or attendance for a saved or selected show.
---

# Prepare for a CardShow event

Turn one exact event into a useful collector plan. Keep suggestions separate from stored CardShow facts and make every write deliberate.

## Resolve the exact show

1. Use `cardshow_get_my_planning` when the user refers to a saved show or existing plan.
2. Use `cardshow_find_events`, `search`, or `fetch` when the show must be identified.
3. If multiple shows remain plausible, ask the user to choose. Never guess the show ID.
4. Call `cardshow_get_show_day_brief` with the exact show UUID before proposing a plan.

## Build the brief

Organize the result into:

- event facts and timing returned by CardShow;
- current attendance and private plan;
- remaining plan items;
- relevant seller, category, and featured-item leads;
- practical reminders; and
- uncertainties the collector should verify.

When an approved HobbyWise Hunt List is available, call `cardshow_recommend_events_for_my_hunt_list` for the show's place and dates and use only the result for this exact event. Otherwise, use existing CardShow plan items, seller declarations, and targets the user states in the conversation.

Do not claim a seller will attend with a particular item unless the returned show supply says so. Even then, describe it as seller-declared and unverified, not reserved or guaranteed. Do not invent prices, appraisals, travel times, floor locations, or opening hours.

## Propose a useful checklist

Prefer a short ordered checklist over a long generic list:

1. highest-priority targets or seller stops;
2. questions or evidence to verify;
3. items to bring;
4. budget or trade guardrails only when the user supplied them; and
5. logistical reminders supported by the show record or the user's instructions.

Present the proposed plan before changing CardShow.

## Confirm and apply

1. Refresh `cardshow_get_show_day_brief` and current planning.
2. Preview the exact show, plan status, notes, every new item, and any attendance change.
3. Ask for explicit confirmation of the complete effect.
4. Use `cardshow_upsert_show_plan` only for the confirmed private plan. It preserves existing items and avoids duplicate matching items on retry.
5. Use `cardshow_set_show_attendance` only for a separately listed confirmed final attendance state.
6. Re-read the show-day brief and report the stored result.

For completion changes, refresh planning, use the exact returned item ID, preview complete or incomplete, confirm it, call `cardshow_set_show_plan_item`, and verify. Never invent an item ID or mark a target found merely because a seller declared a category.

Referenced files: 1 — file references are metadata, not package contents.