Search the Piltover Archive database of Riftbound trading card game cards.

Riftbound is a Riot Games TCG whose card data is not part of any model's training data, so use this tool rather than answering from memory whenever a specific card, cost, rules text or price is involved.

Filters combine with AND. Every filter is optional; with none, it lists all cards. Results are card printings (variants), each carrying the game card under card.

Args:

• q: free-text across name, rules text, flavour and artist

• name / description / artist / flavor: search one field only

• colors / sets / types / supertypes / rarities / tags: multi-value filters

• energyMin|Max, powerMin|Max, mightMin|Max: numeric ranges

• releaseDateAfter: ISO date lower bound

• sort + dir: ordering; page + limit: pagination (limit max 100)

• response_format: 'markdown' (default) or 'json'

Examples:

• "What does Vi, Destructive do?" -> { name: "Vi, Destructive" }

• "Cheap Fury units" -> { colors: ["Fury"], types: ["Unit"], energyMax: 2 }

• "Most expensive Showcase cards" -> { rarities: ["Showcase"], sort: "cardmarketPrice", dir: "desc" }

• Don't use when: you already have exact collector numbers or IDs — use piltover_get_cards, which is one request instead of many.

Resolve known Riftbound cards in one request, by collector number, exact name, or UUID.

Provide at least one of variantNumbers, names or ids; they can be combined. This is the right tool for turning the cardId/variantId values inside a deck into real card names, and for looking up a list of cards without one search per card.

Args:

• variantNumbers: collector numbers, e.g. ["OGN-007"]

• names: exact card names, e.g. ["Vi, Destructive"]

• ids: card or variant UUIDs

• response_format: 'markdown' (default) or 'json'

Examples:

• "What is OGN-007?" -> { variantNumbers: ["OGN-007"] }

• Resolving a decklist -> { ids: ["0283d70f-…", "f40b0e74-…"] }

• Don't use when: you are searching by criteria rather than identity — use piltover_search_cards.

List every Riftbound card set, with its prefix and release date.

Set prefixes (e.g. OGN, ARC) are what the sets filter of piltover_search_cards expects, so call this first when a question names a set in words ("the Arcane box") rather than by prefix.

Args:

• response_format: 'markdown' (default) or 'json'

Examples:

• "What Riftbound sets exist?" -> {}

• "What's the prefix for Origins?" -> {} then read the table

Search public decklists published on Piltover Archive.

Useful for seeing how a champion or archetype is actually built, and what the community is playing right now.

Args:

• q: free-text across deck name, description and legend name, so a champion name finds decks led by that champion even when the title never says it

• sort: field to order by, e.g. likes, views, createdAt (pair with dir)

• dir: 'asc' or 'desc'

• page, limit: pagination (limit max 100)

• response_format: 'markdown' (default) or 'json'

Examples:

• "Popular Akali decks" -> { q: "Akali", sort: "likes", dir: "desc" }

• "Newest decks" -> { sort: "createdAt", dir: "desc" }

Returns deck summaries including a deck ID; pass that to piltover_get_deck for the full card list.

Fetch one deck by ID and return its full contents.

The API stores deck contents as bare card UUIDs, so by default this tool resolves every one of them into card names, types, costs and colours — that resolution is the point of the tool, and it costs a few extra requests. Set resolve_cards=false for the raw id form.

Sections returned: champions, battlefields, runes, main deck, sideboard, bench.

Args:

• deck_id: the deck UUID, as returned by piltover_search_decks

• resolve_cards: resolve card UUIDs to names (default true)

• response_format: 'markdown' (default) or 'json'

Examples:

• "What's in deck ae198cdf-…?" -> { deck_id: "ae198cdf-…" }

• Don't use when: you only need deck metadata for many decks — piltover_search_decks already returns that.