Skip to main content
Glama
kokoa-tools

Korean Independence Patriots Merit Records MCP Server

by kokoa-tools

get_hunkuk_codes

Retrieve honor grade codes for Korean independence patriots to identify and categorize merit records in historical archives.

Instructions

훈격 코드 정보를 조회합니다

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler logic in call_tool function that executes the get_hunkuk_codes tool by formatting and returning the HUNKUK_CODES dictionary.
    elif name == "get_hunkuk_codes":
        # 훈격 코드 정보 조회
        result_json = format_response(HUNKUK_CODES)
        return [
            TextContent(
                type="text",
                text=result_json
            )
        ]
  • Tool registration in list_tools function, including schema with no input properties.
    Tool(
        name="get_hunkuk_codes",
        description="훈격 코드 정보를 조회합니다",
        inputSchema={
            "type": "object",
            "properties": {}
        }
    ),
  • Constant dictionary defining the HUNKUK_CODES used by the tool handler.
    HUNKUK_CODES = {
        "PSG00002": "대한민국장",
        "PSG00003": "대통령장",
        "PSG00004": "독립장",
        "PSG00005": "애국장",
        "PSG00006": "애족장",
        "PSG00007": "건국포장",
        "PSG00008": "대통령표창"
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states this is a retrieval operation ('조회'), implying read-only behavior, but doesn't disclose any behavioral traits like authentication needs, rate limits, response format, or whether it returns all codes or requires filtering. For a tool with zero annotation coverage, this is insufficient disclosure.

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 function. It's front-loaded with the core action and resource, with zero wasted words. This is appropriately sized for a simple retrieval tool with no parameters.

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 lacks behavioral context (e.g., what 'hunkuk codes' are, response format), and with no annotations, it doesn't compensate for missing structured data. For a retrieval tool, more detail on the data returned would be helpful, even without parameters.

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% (empty schema). With no parameters to document, the description doesn't need to add parameter semantics. The baseline for 0 parameters is 4, as there's nothing to compensate for, and the description appropriately focuses on the tool's purpose without unnecessary parameter 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 '훈격 코드 정보를 조회합니다' (Retrieves hunkuk code information) clearly states the verb (조회/retrieve) and resource (훈격 코드/hunkuk codes), establishing basic purpose. However, it doesn't distinguish this from sibling tools like get_merit_list or get_workout_affil_codes, which appear to be similar retrieval operations for different data types. The purpose is understandable but lacks sibling differentiation.

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 doesn't mention prerequisites, appropriate contexts, or exclusions. Given sibling tools like get_merit_list and get_workout_affil_codes that likely retrieve different code sets, the absence of comparative guidance leaves usage unclear.

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