Skip to main content
Glama

get_sets

Read-only

Retrieve detailed information on all Magic: The Gathering card sets, organized by release date in descending order, to support applications or workflows needing comprehensive card data.

Instructions

返回所有MTG卡牌系列的完整数据,按发布日期降序排列

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main execution function for the 'get_sets' tool. It constructs the API URL for fetching all sets and calls the shared response handler.
    async function handleGetSets(config?: z.infer<typeof configSchema>) {
      const url = `${config?.apiUrl || BASE_URL}/sets`;
      const response = await fetch(url);
      return handleSbwszResponse(response);
    }
  • The Tool object defining the 'get_sets' tool, including its name, description, empty inputSchema (no parameters required), and annotations.
    const GET_SETS_TOOL: Tool = {
      name: "get_sets",
      description: "返回所有MTG卡牌系列的完整数据,按发布日期降序排列",
      inputSchema: {
        type: "object",
        properties: {},
        required: []
      },
      annotations: {
        title: "获取所有卡牌系列",
        readOnlyHint: true,
        openWorldHint: true
      }
    };
  • index.ts:511-513 (registration)
    Registration of the 'get_sets' handler in the switch statement within the CallToolRequestSchema handler.
    case "get_sets": {
      return await handleGetSets(config);
    }
  • index.ts:269-276 (registration)
    Inclusion of GET_SETS_TOOL in the SBWSZ_TOOLS array, which is returned by listTools and used for tool discovery.
    const SBWSZ_TOOLS = [
      GET_CARD_BY_SET_AND_NUMBER_TOOL,
      SEARCH_CARDS_TOOL,
      GET_SETS_TOOL,
      GET_SET_TOOL,
      GET_SET_CARDS_TOOL,
      HZLS_TOOL
    ] as const;
  • index.ts:487-489 (registration)
    MCP server registration for ListToolsRequestSchema, which provides the list of tools including 'get_sets'.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: SBWSZ_TOOLS
    }));
Behavior3/5

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

The description adds minimal behavioral context beyond annotations. Annotations already declare readOnlyHint=true (safe read operation) and openWorldHint=true (data may change), so the agent knows it's non-destructive and dynamic. The description only adds sorting behavior ('按发布日期降序排列'), which is useful but limited. No other traits like rate limits, auth needs, or response format are disclosed, but with annotations covering safety, this meets baseline expectations.

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

Conciseness5/5

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

The description is a single, efficient sentence in Chinese that conveys the core action, resource, and sorting behavior without any waste. It's front-loaded with the main purpose ('返回所有MTG卡牌系列的完整数据') and adds only essential detail. Every word earns its place, making it highly concise and well-structured.

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

Completeness3/5

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

Given the tool's simplicity (0 parameters, read-only with open-world hints, no output schema), the description is adequate but not fully complete. It explains what the tool does and sorting, but lacks details on response format (e.g., structure of returned data) or potential limitations (e.g., pagination). With annotations handling safety, it meets minimum viability, but could be more informative for an agent invoking it.

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?

The tool has 0 parameters, with 100% schema description coverage (empty schema). The description doesn't need to explain parameters, as there are none. It appropriately focuses on the tool's function without redundant parameter info, earning a high score for this context.

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

Purpose4/5

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

The description clearly states the tool's purpose: '返回所有MTG卡牌系列的完整数据' (returns complete data for all MTG card sets). It specifies the verb ('返回' - return) and resource ('MTG卡牌系列' - MTG card sets), and mentions the sorting order ('按发布日期降序排列' - sorted by release date descending). However, it doesn't explicitly distinguish this from sibling tools like 'get_set' (singular) or 'get_set_cards', which slightly limits differentiation.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like 'get_set' (for a single set) or 'get_set_cards' (for cards within a set), nor does it specify use cases or exclusions. The agent must infer usage from the tool name and description alone, which is insufficient for optimal selection.

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

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lieyanqzu/sbwsz-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server