Skip to main content
Glama

get_set

Read-only

Fetch detailed information for a Magic: The Gathering card series using its set code. Ideal for accessing specific data from the sbwsz-mcp server for applications or workflows.

Instructions

根据系列代码获取单个系列的详细信息

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
set_codeYes系列代码,例如 'NEO'、'MOM'

Implementation Reference

  • The handler function that executes the 'get_set' tool logic: constructs the API URL using the set_code parameter and fetches the set details from the SBWSZ API.
    async function handleGetSet(setCode: string, config?: z.infer<typeof configSchema>) {
      const url = `${config?.apiUrl || BASE_URL}/set/${encodeURIComponent(setCode.toUpperCase())}`;
      const response = await fetch(url);
      return handleSbwszResponse(response);
    }
  • The Tool definition for 'get_set', including name, description, input schema (requiring 'set_code' string), and annotations.
    const GET_SET_TOOL: Tool = {
      name: "get_set",
      description: "根据系列代码获取单个系列的详细信息",
      inputSchema: {
        type: "object",
        properties: {
          set_code: {
            type: "string",
            description: "系列代码,例如 'NEO'、'MOM'"
          }
        },
        required: ["set_code"]
      },
      annotations: {
        title: "获取单个系列的详细信息",
        readOnlyHint: true,
        openWorldHint: true
      }
    };
  • index.ts:514-517 (registration)
    Registers and dispatches 'get_set' tool calls in the MCP CallToolRequestSchema handler by extracting 'set_code' from arguments and invoking the handler.
    case "get_set": {
      const { set_code } = args as { set_code: string };
      return await handleGetSet(set_code, config);
    }
  • index.ts:269-276 (registration)
    Includes the GET_SET_TOOL in the array of tools returned by listTools request.
    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;
Behavior3/5

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

Annotations already provide readOnlyHint=true and openWorldHint=true, so the agent knows this is a safe read operation that may return partial results. The description adds minimal behavioral context beyond this - it specifies this retrieves '详细信息' (detailed information) which suggests comprehensive data, but doesn't describe format, limitations, or what constitutes 'detailed' information. With annotations covering the safety profile, a baseline 3 is appropriate as the description adds some value but not rich behavioral context.

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 that communicates the core purpose without any wasted words. It's appropriately sized for a simple retrieval tool with one parameter. The structure is front-loaded with the essential information - what the tool does and what it requires. Every word earns its place in this concise description.

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?

For a simple read operation with good annotations (readOnlyHint, openWorldHint) and complete schema coverage, the description is minimally adequate. However, without an output schema, the description doesn't explain what '详细信息' (detailed information) includes or the return format. Given the tool's simplicity and good annotation coverage, the description meets basic requirements but could better address what constitutes the returned 'detailed information'.

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

Parameters3/5

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

Schema description coverage is 100%, with the single parameter 'set_code' well-documented in the schema (including examples like 'NEO', 'MOM'). The description doesn't add any parameter semantics beyond what the schema already provides - it mentions '系列代码' (series code) which is already covered in the schema. With complete schema coverage, the baseline 3 is appropriate as the schema does the heavy lifting.

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 action ('获取' - get/retrieve) and resource ('单个系列的详细信息' - detailed information of a single series), making the purpose immediately understandable. It doesn't specifically differentiate from sibling tools like 'get_sets' (which likely retrieves multiple series), but the focus on a single series is clear. The description avoids tautology by providing meaningful context beyond just the tool name.

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. There are several sibling tools that appear related (get_sets, get_set_cards, get_card_by_set_and_number), but the description doesn't indicate when this specific single-series retrieval tool is appropriate versus those other options. No context about prerequisites, limitations, or appropriate scenarios is provided.

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