Cardspark — Your collection, in every conversation

• Search the global card catalog — Search cards beyond the user's collection or tracker with a provider-neutral, saveable definition. Put only the card name in text and put collector or printed numbers such as 204/198 in filters.numbers; use filters instead of Scrydex syntax. Returns at most nine exact printings per page and raw Near Mint prices unless a different market basis is requested.
• Save a card search — Save or rename one normalized global card search for the signed-in user. This creates quick access only; it does not create a subscription or notification.
• List saved card searches — List the signed-in user's private saved card searches. Saved searches are quick-access definitions, not notification subscriptions.
• Delete a saved card search — Delete one private saved search only when the user explicitly asks to remove or unsave it.
• Save a Cardspark view preference — App-only action that remembers the signed-in user's grid or list preference for one Cardspark surface.
• Show my current Cardspark collection — Use this when the user asks to show, view, list, browse, inspect, summarize, or discuss their Cardspark collection, including the exact request 'show me my Cardspark collection.' This is the required first action for that request: call it immediately in the same turn, even if earlier messages or memory contain collection totals. Never answer from cached conversational context and never merely promise to retrieve the collection. It returns the current authenticated collection and visibly renders
• Query a Cardspark collection page — App-only collection query used by the rendered Cardspark collection to apply filters, sorting, and pagination. Models should use show_my_collection for human requests to show or discuss the collection. Use artist for illustrator filters.
• Resolve one collected card for a report — Model-only resolver for a human-facing report about one card selected from the authenticated user's collection, including superlatives such as most valuable, newest, oldest, biggest gain, or biggest decline. Apply the requested filters and sort, then immediately call get_card_report exactly once with item.report_arguments when found is true. Do not call show_my_collection before or after this tool, and do not stop after resolving the holding.
• Get my Cardspark collection summary — Use this only when the user explicitly asks for a compact numerical collection summary without showing cards or the collection UI. Returns current counts and value totals for the authenticated user's default Cardspark collection. Do not use it when the user asks to show, view, browse, list, inspect, or discuss their collection; use show_my_collection instead.
• View my tracked cards — Browses the authenticated user's tracked exact cards and variants with server-side search, freshness filtering, sorting, and cursor pagination. Prices use the raw Near Mint quote basis; tracked cards are not owned collection holdings and do not have quantities, conditions, graders, or grades.
• Track a confirmed card variant — Tracks one exact, user-confirmed card and printing variant using raw Near Mint as its canonical price basis. This does not add an owned holding, quantity, condition, grader, or grade. Reuse the same idempotency key when retrying the same request.
• Track confirmed card variants — Atomically tracks between 1 and 50 exact, user-confirmed cards and printing variants in one request using raw Near Mint as the canonical price basis. Already-tracked targets are preserved and reported as unchanged. This does not add owned holdings, quantities, conditions, graders, or grades. Reuse the same idempotency key when retrying the same batch.
• Stop tracking a card variant — Stops tracking one exact card and printing variant. This does not change any owned collection holding. Reuse the same idempotency key when retrying the same request.
• Review pictured cards to add — Use only when the user wants to add one or more cards shown in an image to their Cardspark collection. The image stays with the chat host; send only structured observations here. Cardspark resolves possible exact printings and opens a human review surface; nothing is added until the user confirms there. Do not use this tool for identification, lookup, or valuation-only requests; use search_catalog instead. Include every visible card once, use quantity for true duplicates, preserve a short image_
• Add reviewed cards to my Cardspark collection — Atomically adds or increments up to 50 exact, user-confirmed card identities and complete market selections in the authenticated user's default collection. Use only after human review. Reuse the same idempotency key when retrying the same batch.
• Get valid Cardspark collection item choices — Returns the durable cached market selections currently available for one owned collection item. Use these exact choices before updating a holding; this does not change the confirmed card identity.
• Add a confirmed card to my Cardspark collection — Adds or increments one exact, user-confirmed card and complete market selection in the authenticated user's default collection. Reuse the same idempotency key when retrying the same request.
• Set a Cardspark collection item quantity — Sets the positive quantity of an owned item in the authenticated user's default collection. Reuse the same idempotency key when retrying the same request.
• Update a Cardspark collection item — Updates one owned holding's absolute quantity and complete market selection without changing its confirmed card identity. Use a selection returned by get_collection_item_edit_options. If the destination selection already exists, Cardspark merges the quantities atomically. Reuse the same idempotency key when retrying the same request.
• Remove a Cardspark collection item — Removes one owned item from the authenticated user's default collection. Reuse the same idempotency key when retrying the same request.
• Get a card report — Use this whenever the user asks for a report, full report, market report, deep dive, dated history, sold-listing evidence, or population context for one exact card. If resolve_collection_card supplied report_arguments, pass them through exactly. For a card found through search_catalog, pass that exact identity directly. Edge accounts receive authorized deep features. A verified Free account receives the existing exact search-result view instead of an entitlement error. If the request does not re
• Look up a sealed product — Use this when a user asks what a booster pack, booster box, Elite Trainer Box, or other sealed product is worth. Resolves a human description and returns the matching product, images, variants, current raw prices, currencies, and trend windows. Supports Pokémon, One Piece, and Riftbound.
• Search trading-card expansions and sets — Use this to find expansion IDs or answer set-catalog questions by name, series, type, language, release date, or card count. The query uses Scrydex Lucene-style syntax, for example language:Japanese release_date:[2025/01/01 TO 2025/12/31]. Use returned IDs with compare_expansion_markets.
• Compare expansion market trends — Use this after search_expansions to compare up to five set IDs. Builds a transparent raw-card market index by summing one copy of each priced variant in the requested condition, reports trend coverage, and ranks sets by Scrydex's 1, 7, 14, 30, 90, or 180-day changes. It is not sales-volume weighted.
• Search trading cards — Low-level model-only Scrydex search for exact-ID resolution when a workflow already has a provider query. For human-facing discovery, lookup, and current-value results, use search_catalog.

Showing the first 25 tools — full list and schemas: Directory API.