Skip to main content
Glama

list_sets

Use this for any question about set names, including mapping a Japanese set title such as Ruler of the Black Flame to Obsidian Flames. Filter by name and an optional game slug (pokemon, mtg, yugioh, onepiece, riftbound) or language en/ja. Each row includes id, name, game, language, and release_date. Free, limited to 60 per minute and 1000 per key per UTC day, shared with the other free catalog calls.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_sets"
  }
}

Input Schema

NameRequiredDescriptionDefault
gameNoOptional game slug.
nameNoSet name or fragment, for example Obsidian Flames or Ruler of the Black Flame.
languageNoOptional language filter.

Output Schema

NameRequiredDescriptionDefault
setsNo
totalNo
truncatedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations supplied, the description carries the full burden and does well: it discloses cost (free), two concrete rate limits (60/minute, 1000 per key per UTC day), and that the quota is shared across other free catalog calls. It does not address authentication requirements or whether results are truncated/paginated, which is the main remaining gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the use case, then filters, then return fields, then limits – a sensible order with no filler sentences. The rate-limit sentence is a bit dense, and listing row fields duplicates the existing output schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 3-parameter, no-required-arg lookup tool with an output schema, the description covers purpose, filters, quota, and cost adequately. Minor redundancy in restating return fields, and no mention of result-size behavior, but nothing an agent needs to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds real meaning: it enumerates the accepted game slugs and language codes in one place and gives example name fragments including a Japanese title. It doesn't clarify whether `name` is a prefix match, substring, or fuzzy match, which matters for a free-text filter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (list sets, filtered by name/game/language) and anchors it with a concrete use case: mapping a Japanese set title such as 'Ruler of the Black Flame' to 'Obsidian Flames'. This makes it clearly distinguishable from the card-level siblings like find_card and get_card.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Opens with an explicit when-to-use rule ('any question about set names') and adds the resolution/mapping scenario, which is the key selection signal versus card search tools. It stops short of naming an alternative or stating when NOT to use it, so it falls just short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources