Skip to main content
Glama
hyunhoonj

Youth Activity Information MCP Server

by hyunhoonj

echo

Tests connectivity and validates input parameters for the Youth Activity Information MCP Server by returning provided messages unchanged.

Instructions

입력받은 메시지를 그대로 반환합니다

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageYes반환할 메시지

Implementation Reference

  • The handler function for the 'echo' tool. It extracts the 'message' from the arguments and returns it as text content prefixed with 'Echo:'.
    case "echo": {
      const message = args?.message as string;
      return {
        content: [
          {
            type: "text",
            text: `Echo: ${message}`,
          },
        ],
      };
    }
  • The tool definition including name, description, and input schema for the 'echo' tool, used for registration in the ListToolsRequestSchema handler.
    {
      name: "echo",
      description: "입력받은 메시지를 그대로 반환합니다",
      inputSchema: {
        type: "object",
        properties: {
          message: {
            type: "string",
            description: "반환할 메시지",
          },
        },
        required: ["message"],
      },
    },
    {
  • src/index.ts:54-188 (registration)
    The echo tool is registered by including its definition in the response of the ListToolsRequestSchema handler.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: [
          // 청소년 활동 API 관련 도구
          {
            name: "get_sido_list",
            description: "청소년 활동 정보 시도(광역자치단체) 목록을 조회합니다",
            inputSchema: {
              type: "object",
              properties: {
                pageNo: {
                  type: "number",
                  description: "페이지 번호 (기본값: 1)",
                },
                numOfRows: {
                  type: "number",
                  description: "한 페이지 결과 수 (기본값: 100)",
                },
              },
            },
          },
          {
            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"],
            },
          },
          {
            name: "search_youth_activities",
            description: "청소년 활동 프로그램을 검색합니다. 프로그램명, 기관명, 지역, 기간 등으로 필터링 가능합니다",
            inputSchema: {
              type: "object",
              properties: {
                pageNo: {
                  type: "number",
                  description: "페이지 번호 (기본값: 1)",
                },
                numOfRows: {
                  type: "number",
                  description: "한 페이지 결과 수 (기본값: 10)",
                },
                atName: {
                  type: "string",
                  description: "프로그램명 (선택사항)",
                },
                orgName: {
                  type: "string",
                  description: "주최자(기관명) (선택사항)",
                },
                sido: {
                  type: "string",
                  description: "시도명 (선택사항, 예: 서울, 부산광역시)",
                },
                startDate: {
                  type: "string",
                  description: "일활동기간시작일 (선택사항, YYYYMMDD 형식)",
                },
                endDate: {
                  type: "string",
                  description: "일활동기간종료일 (선택사항, YYYYMMDD 형식)",
                },
              },
            },
          },
          {
            name: "get_facility_group_list",
            description: "청소년 시설 그룹 목록을 조회합니다. 시도, 기관명, 기관유형으로 필터링 가능합니다",
            inputSchema: {
              type: "object",
              properties: {
                pageNo: {
                  type: "number",
                  description: "페이지 번호 (기본값: 1)",
                },
                numOfRows: {
                  type: "number",
                  description: "한 페이지 결과 수 (기본값: 10)",
                },
                sido: {
                  type: "string",
                  description: "시도명 (선택사항)",
                },
                stName: {
                  type: "string",
                  description: "기관명 (선택사항)",
                },
                gName: {
                  type: "string",
                  description: "기관유형명 (선택사항)",
                },
              },
            },
          },
          // 기본 유틸리티 도구
          {
            name: "echo",
            description: "입력받은 메시지를 그대로 반환합니다",
            inputSchema: {
              type: "object",
              properties: {
                message: {
                  type: "string",
                  description: "반환할 메시지",
                },
              },
              required: ["message"],
            },
          },
          {
            name: "get_time",
            description: "현재 시간을 반환합니다",
            inputSchema: {
              type: "object",
              properties: {},
            },
          },
        ],
      };
    });
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 only states the basic function of echoing a message, without mentioning any behavioral traits such as error handling, performance characteristics, or side effects. For a tool with no annotations, this is a significant gap in transparency.

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, clear sentence that directly states the tool's function without any unnecessary words. It is front-loaded and efficiently conveys the core purpose, making it highly concise and well-structured for quick understanding.

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 (one parameter, no output schema, no annotations), the description is minimally adequate. It covers the basic purpose but lacks details on usage guidelines and behavioral transparency. For a straightforward echo tool, this might be sufficient, but it does not fully address all contextual aspects like when to use it or potential limitations.

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 schema description coverage is 100%, with the parameter 'message' fully documented in the schema as '반환할 메시지' (message to return). The description does not add any additional meaning or context beyond what the schema provides, such as format examples or constraints. Given the high schema coverage, a baseline score of 3 is appropriate.

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 function: '입력받은 메시지를 그대로 반환합니다' translates to 'Returns the received message as is.' This specifies the verb ('returns') and resource ('message'), making the purpose unambiguous. However, it does not differentiate from sibling tools, which are unrelated (e.g., get_facility_group_list, get_time), so it lacks sibling distinction.

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 states what the tool does but does not mention any context, prerequisites, or exclusions for usage. There is no implied or explicit advice on scenarios where this tool is appropriate, leaving the agent without usage direction.

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