Skip to main content
Glama
hyunhoonj

Youth Activity Information MCP Server

by hyunhoonj

get_time

Retrieve current time for scheduling youth activities and coordinating programs through the Youth Activity Information MCP Server.

Instructions

현재 시간을 반환합니다

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler for the 'get_time' tool. It creates a new Date object and returns the current time in both ISO format and local Korean locale as text content.
    case "get_time": {
      const now = new Date();
      return {
        content: [
          {
            type: "text",
            text: `현재 시간: ${now.toISOString()}\n로컬 시간: ${now.toLocaleString(
              "ko-KR"
            )}`,
          },
        ],
      };
    }
  • The input schema definition for the 'get_time' tool as returned by listTools. It has no required input properties.
    {
      name: "get_time",
      description: "현재 시간을 반환합니다",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • src/index.ts:56-187 (registration)
    The tool is registered in the ListToolsRequestSchema handler by including it in the tools array.
      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 states the tool returns the current time, but doesn't specify format (e.g., timestamp, string), timezone, or any side effects. For a tool with zero annotation coverage, 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: '현재 시간을 반환합니다' (Returns the current time). It's front-loaded with the core purpose, has zero waste, and is appropriately sized for a simple tool with no parameters.

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, no output schema), the description is minimally adequate. It states what the tool does but lacks details on return format or behavioral context. Without annotations or output schema, it doesn't fully prepare an agent for invocation, though it's sufficient for basic understanding.

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, and schema description coverage is 100%, so there's no need for parameter details in the description. The baseline for this scenario is 4, as the description appropriately focuses on the tool's function without redundant parameter information.

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: '현재 시간을 반환합니다' (Returns the current time). This specifies the verb (returns) and resource (current time), making it immediately understandable. However, it doesn't differentiate from sibling tools like 'echo' or 'search_youth_activities', which prevents a perfect score.

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's no mention of context, prerequisites, or comparisons to sibling tools like 'get_facility_group_list' or 'get_sido_list'. The user must infer usage based solely on the tool name and description.

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