Skip to main content
Glama
shinkeonkim

독립유공자 공훈록 MCP 서버

by shinkeonkim

get_workout_affil_codes

Retrieve exercise-related affiliation codes for Korean independence activists from the national veterans' database.

Instructions

운동계열 코드 정보를 조회합니다

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler logic for the get_workout_affil_codes tool. It formats the WORKOUT_AFFIL_CODES dictionary using format_response and returns it as TextContent.
    elif name == "get_workout_affil_codes":
        # 운동계열 코드 정보 조회
        result_json = format_response(WORKOUT_AFFIL_CODES)
        return [
            TextContent(
                type="text",
                text=result_json
            )
        ]
  • Tool registration in list_tools() function, defining name, description, and empty input schema.
    Tool(
        name="get_workout_affil_codes",
        description="운동계열 코드 정보를 조회합니다",
        inputSchema={
            "type": "object",
            "properties": {}
        }
    ),
  • The WORKOUT_AFFIL_CODES dictionary containing the code-value pairs for workout affiliations, used by the tool handler.
    WORKOUT_AFFIL_CODES = {
        "UGC00002": "의병",
        "UGC00003": "3.1운동",
        "UGC00004": "문화운동",
        "UGC00005": "국내항일",
        "UGC00006": "의열투쟁",
        "UGC00007": "학생운동",
        "UGC00008": "광복군",
        "UGC00009": "계몽운동",
        "UGC00010": "임시정부",
        "UGC00011": "일본방면",
        "UGC00012": "만주방면",
        "UGC00013": "중국방면",
        "UGC00014": "노령방면",
        "UGC00015": "미주방면",
        "UGC00017": "인도네시아방면",
        "UGC00023": "독립운동지원",
        "UGC00024": "구주방면"
    }
Behavior2/5

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

With no annotations provided, the description carries full burden but only states it retrieves information, implying a read-only operation. It lacks details on behavioral traits like rate limits, authentication needs, error handling, or what '정보' (information) entails in terms of format or scope, which is insufficient for a tool with zero annotation coverage.

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

Conciseness4/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 action and resource. It's front-loaded with the core purpose, though it could be slightly more structured if it included minor usage hints without adding bulk.

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 simplicity (0 parameters, no output schema), the description is minimal but incomplete. It doesn't explain the return values or what 'code information' includes, and with no annotations, it fails to provide necessary context like data format or typical use cases, leaving gaps for an agent to understand full functionality.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter details, but this is acceptable as there are no parameters to explain. A baseline of 4 is appropriate since the schema fully covers the absence of parameters.

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

Purpose3/5

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

The description states the purpose ('조회합니다' meaning 'retrieves' or 'looks up') and resource ('운동계열 코드 정보' meaning 'exercise series code information'), which is clear but basic. It doesn't differentiate from sibling tools like 'get_hunkuk_codes' or 'get_merit_list', leaving ambiguity about what makes this specific code type distinct.

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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention context, prerequisites, or exclusions, such as whether it's for reference data, filtering, or if other tools handle related codes. This leaves the agent without direction on appropriate usage scenarios.

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/shinkeonkim/e-gonghun-mcp'

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