Skip to main content
Glama
kokoa-tools

Korean Independence Patriots Merit Records MCP Server

by kokoa-tools

get_workout_affil_codes

Retrieve movement affiliation codes to filter Korean independence patriot records by their historical activism groups.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'get_workout_affil_codes' tool. It formats the WORKOUT_AFFIL_CODES dictionary into JSON 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
            )
        ]
  • Registers the 'get_workout_affil_codes' tool in the list_tools() function, including its name, description, and empty input schema.
    Tool(
        name="get_workout_affil_codes",
        description="운동계열 코드 정보를 조회합니다",
        inputSchema={
            "type": "object",
            "properties": {}
        }
    ),
  • The input schema for the tool, which is an empty object (no parameters required).
    inputSchema={
        "type": "object",
        "properties": {}
    }
  • Constant dictionary defining the workout affiliation codes (key-value pairs) that the tool returns.
    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?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states that it retrieves information, implying a read-only operation, but doesn't add context such as whether it requires authentication, has rate limits, returns structured data, or any other behavioral traits. This is a significant gap for a tool with no 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.

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 action and resource without any waste. It is appropriately sized and front-loaded, making it easy to parse quickly.

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, no annotations), the description is minimal. It states the basic purpose but lacks completeness for effective use: no information on output format, error handling, or behavioral context. For a retrieval tool, this leaves gaps in understanding how to interpret results or handle edge cases.

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 are no parameters to document. The description doesn't need to add parameter semantics, and it appropriately doesn't mention any. Baseline is 4 for zero parameters, as it avoids unnecessary details.

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 a purpose ('조회합니다' meaning 'retrieve' or 'look up') and specifies the resource ('운동계열 코드 정보' meaning 'exercise series code information'), which is clear. However, it doesn't differentiate from sibling tools like 'get_hunkuk_codes' or 'get_merit_list' in terms of what specific codes or data it retrieves, making it somewhat vague in context.

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. The description does not mention any context, prerequisites, or exclusions, and it doesn't reference sibling tools or scenarios where this tool is preferred over others, 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/kokoa-tools/e-gonghun-mcp'

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