list_setsList every Pokémon TCG Pocket set with its id and localized name. Use the ids to filter search_cards by set.
| Name | Required | Description | Default |
|---|---|---|---|
| locale | No | Locale for set names. Defaults to 'en'. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already declare readOnlyHint=true, and the description goes beyond them by specifying the output includes ids and localized names, and that the list is exhaustive ('every'). It doesn't mention ordering or pagination, but for a read-only list tool this is reasonably transparent.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two tightly written sentences with no filler. The core behavior is front-loaded, and the usage guidance is delivered in a single actionable sentence.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple read-only tool with zero required parameters and a full schema, the description provides enough context: it names the resource, the return shape, and the workflow. No output schema exists, but the description covers the essential return information.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage for the only parameter, locale, is 100% and the schema already states its purpose and default. The description adds the context that set names are localized, which slightly reinforces the parameter's meaning, but the schema carries the semantic weight.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb ('List'), a clear resource ('every Pokémon TCG Pocket set'), and the returned fields ('id and localized name'). It also connects directly to a sibling tool ('search_cards') by explaining how the ids are meant to be used, distinguishing its purpose.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly tells the agent when to use the tool's output: to filter search_cards by set. It doesn't spell out exclusions or alternatives like list_packs or list_printings, but the intended workflow is clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clearly distinct purpose: catalog metadata, search, single-card retrieval, printings, sets, packs, locales, and deck validation/creation/testing/simulation are all cleanly separated. Even the deck-related tools are unambiguous because each targets a different stage: validate, suggest, trial, or matchup.
The vast majority of tools follow a predictable verb_noun pattern (list_sets, get_card, search_cards, simulate_matchup, evaluate_deck). The only outlier is catalog_info, which uses a noun_info form instead of an imperative verb, creating a minor but noticeable deviation.
At 11 tools, the server is well-scoped for its domain of card-catalog lookup and deck analysis. Each tool covers a distinct function and none feel redundant or unnecessary.
The catalog surface is strong with search, get, list, and metadata tools, and the deck workflow covers validation, suggestion, solo trialing, and matchups. Minor gaps exist: search_cards returns at most 20 results with no pagination, and there are no detailed set/pack getters, but agents can work around these with existing tools.