> For the complete documentation index, see [llms.txt](https://studio0.gitbook.io/tome-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://studio0.gitbook.io/tome-docs/card-lookup.md). # Card Lookup | Command | What it does | | ------------------------------------ | --------------------------------------------------- | | `%card ` | Look at a card and flip through all its art | | `%view [@user]` | Look at one specific card you (or someone else) own | | `%lu [@user]` | See what a card's worth, see Card Valuation | | `%catalog [search]` | Browse every card in the bot | | `%series [@user]` | See every card in a series, marked for what's owned | ## `%card`, looking up a card Shows the name, the series it's from, how many people own a copy, and how many copies exist total, then lets you flip through every piece of art it has with Previous and Next buttons. If there's more than one kind of art (normal, posters, misprints, misprint posters), you get a dropdown to jump straight to whichever kind you want. Doesn't matter how you capitalize the name. If a name shows up in more than one series, add `| seriesname` to be specific, like `%card vergil | dmc`. Nicknames like `dmc` work here too. Leave the series off and it's genuinely unclear which one you mean? You'll get a dropdown to pick from instead of an error. You don't need to type the whole name either. A partial match, like just `%card gou`, works fine as long as it's not ambiguous. If a few different characters all match what you typed, you'll get a **Multiple Matches** list numbered 1, 2, 3 and so on, just reply with the number of the one you want. ## `%view`, checking one card you own Shows the exact stars, mint number (`#123`, `MP#123` for a misprint, or a plain `C` for a compensation grant, see Other Commands), card code, who owns it, how many people have it wishlisted, and any tags on it. It shows up with whatever frame is equipped on that specific card, see Frames. Takes a Card ID or a card code. A plain number gets treated as a Card ID (yours by default, add `@user` to check someone else's). Anything else is treated as a card code, which works no matter who owns it, so you can `%view` any card code even if it's not yours. ## `%catalog`, browsing everything Lists every card in the bot, sorted by series then name, and tells you how much art each one has (or if it has none yet). Add a search to narrow it down by name or series. This is different from `%collection`, which only shows what you personally own. `%catalog` shows the whole pool of cards that exist. ## `%series`, browsing a series Lists every card in a series with a checkmark next to whichever ones you (or whoever you mention) already own, plus a little count in the title. Good for keeping track of how close you are to a set completion reward. Works with nicknames as well as the full series name, and doesn't need to be exact either. If what you typed matches more than one series, you'll get a picker to choose from. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://studio0.gitbook.io/tome-docs/card-lookup.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.