Skip to main content
Glama
hyunhoonj

Youth Activity Information MCP Server

by hyunhoonj

get_sigungu_list

Retrieve a list of districts (sigungu) within a specific province or metropolitan city in South Korea to enable regional filtering for youth activity searches.

Instructions

특정 시도의 시군구(기초자치단체) 목록을 조회합니다

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sidoYes시도명 (예: 서울, 부산광역시, 경기도)
pageNoNo페이지 번호 (기본값: 1)
numOfRowsNo한 페이지 결과 수 (기본값: 100)

Implementation Reference

  • MCP tool handler for 'get_sigungu_list': extracts parameters from args, calls youthApiClient.getSigunguList, formats the paginated list of sigungu (districts) with names and codes into a readable text response.
    case "get_sigungu_list": {
      const sido = args?.sido as string;
      const pageNo = (args?.pageNo as number) || 1;
      const numOfRows = (args?.numOfRows as number) || 100;
    
      const result = await youthApiClient.getSigunguList(
        sido,
        pageNo,
        numOfRows
      );
    
      let resultText = `📍 시군구 목록 (전체 ${result.totalCount}개)\n\n`;
      if (Array.isArray(result.items)) {
        result.items.forEach((item: any, index: number) => {
          resultText += `${index + 1}. ${item.sigunguNm || "N/A"} (코드: ${
            item.sigunguCode || "N/A"
          })\n`;
        });
      } else if (result.items) {
        resultText += `1. ${result.items.sigunguNm || "N/A"} (코드: ${
          result.items.sigunguCode || "N/A"
        })\n`;
      } else {
        resultText += "조회된 항목이 없습니다.\n";
      }
      resultText += `\n페이지: ${pageNo}/${Math.ceil(
        result.totalCount / numOfRows
      )}`;
    
      return {
        content: [
          {
            type: "text",
            text: resultText,
          },
        ],
      };
    }
  • src/index.ts:75-96 (registration)
    Tool registration in ListTools handler: defines name, description, and input schema requiring 'sido' (province name) with optional pagination.
    {
      name: "get_sigungu_list",
      description: "특정 시도의 시군구(기초자치단체) 목록을 조회합니다",
      inputSchema: {
        type: "object",
        properties: {
          sido: {
            type: "string",
            description: "시도명 (예: 서울, 부산광역시, 경기도)",
          },
          pageNo: {
            type: "number",
            description: "페이지 번호 (기본값: 1)",
          },
          numOfRows: {
            type: "number",
            description: "한 페이지 결과 수 (기본값: 100)",
          },
        },
        required: ["sido"],
      },
    },
  • YouthApiClient method that performs the actual API call to '/getSigunguList', sends params including serviceKey and sido (province name), parses XML response, validates resultCode, extracts totalCount and items, handles errors.
    async getSigunguList(
      sido: string,
      pageNo: number = 1,
      numOfRows: number = 100
    ): Promise<any> {
      try {
        const response = await this.client.get("/getSigunguList", {
          params: {
            serviceKey: this.serviceKey,
            sido,
            pageNo,
            numOfRows,
          },
        });
    
        const parsedData = await this.parseXmlResponse(response.data);
    
        if (parsedData.response) {
          const header = parsedData.response.header;
          const body = parsedData.response.body;
    
          if (header?.resultCode !== "00") {
            throw new Error(
              `API 오류: ${header?.resultMsg || "알 수 없는 오류"}`
            );
          }
    
          return {
            totalCount: parseInt(body?.totalCount || "0"),
            items: body?.items?.item || [],
            pageNo,
            numOfRows,
          };
        }
    
        throw new Error("예상치 못한 응답 형식");
      } catch (error) {
        if (axios.isAxiosError(error)) {
          throw new Error(
            `API 호출 실패: ${error.message}${
              error.response?.data ? ` - ${error.response.data}` : ""
            }`
          );
        }
        throw error;
      }
    }
  • Input schema definition for the tool: object with required 'sido' string, optional 'pageNo' and 'numOfRows' numbers.
    inputSchema: {
      type: "object",
      properties: {
        sido: {
          type: "string",
          description: "시도명 (예: 서울, 부산광역시, 경기도)",
        },
        pageNo: {
          type: "number",
          description: "페이지 번호 (기본값: 1)",
        },
        numOfRows: {
          type: "number",
          description: "한 페이지 결과 수 (기본값: 100)",
        },
      },
      required: ["sido"],
    },
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool retrieves a list, implying a read-only operation, but doesn't disclose other traits such as pagination behavior (implied by pageNo and numOfRows parameters), rate limits, authentication needs, error handling, or response format. For a tool with parameters and no annotations, this leaves significant gaps in understanding its behavior.

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 Korean that directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, making it easy to understand quickly. Every part of the sentence contributes to clarifying the tool's function.

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

Completeness2/5

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

Given the tool's complexity (3 parameters, no output schema, no annotations), the description is incomplete. It adequately states what the tool does but lacks details on behavior, output, and usage context. Without annotations or an output schema, the description should provide more context about the retrieval process, result format, or limitations to be fully helpful for an AI agent.

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?

The description adds minimal meaning beyond the input schema. It mentions '특정 시도의' (for a specific province), which aligns with the 'sido' parameter, but doesn't elaborate on parameter interactions or usage. With 100% schema description coverage, the schema already documents all parameters (sido, pageNo, numOfRows) with descriptions and defaults. The description doesn't compensate with additional insights, so it meets the baseline for high schema coverage.

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: '특정 시도의 시군구(기초자치단체) 목록을 조회합니다' translates to 'Retrieves a list of districts (basic local governments) for a specific province.' This specifies the verb (조회/retrieve) and resource (시군구 목록/district list) with a scope constraint (특정 시도/for a specific province). However, it doesn't explicitly differentiate from siblings like get_sido_list, which retrieves province lists rather than district lists for a province.

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 (e.g., get_sido_list for province lists or search_youth_activities for other data), prerequisites, or exclusions. Usage is implied by the purpose but lacks explicit context for selection among available tools.

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

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/hyunhoonj/mcp-test'

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