Skip to main content
Glama
kokoa-tools

Korean Independence Patriots Merit Records MCP Server

by kokoa-tools

clear_cache

Clear cached data to ensure access to current Korean independence patriot records and achievement documents from the Ministry of Patriots and Veterans Affairs archives.

Instructions

캐시된 데이터를 모두 초기화합니다

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The execution handler for the 'clear_cache' tool. It invokes cache_manager.clear() and returns a formatted success response.
    elif name == "clear_cache":
        # 캐시 초기화
        cache_manager.clear()
        return [
            TextContent(
                type="text",
                text=format_response({
                    "success": True,
                    "message": "캐시가 성공적으로 초기화되었습니다."
                })
            )
        ]
  • Registration of the 'clear_cache' tool in the list_tools() function, including its name, description, and empty input schema.
    Tool(
        name="clear_cache",
        description="캐시된 데이터를 모두 초기화합니다",
        inputSchema={
            "type": "object",
            "properties": {}
        }
    )
  • The CacheManager.clear() method that implements the actual cache clearing logic by emptying the cache dictionaries and logging the event.
    def clear(self) -> None:
        """모든 캐시를 초기화합니다."""
        self.last_cache_time.clear()
        self.cache_data.clear()
        logger.info("캐시가 초기화되었습니다.")
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It indicates a destructive action ('초기화합니다' implies clearing/resetting), but doesn't specify what '모든' (all) encompasses, whether this requires special permissions, if it's reversible, or what side effects might occur. For a mutation tool with zero annotation coverage, this is insufficient.

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 that directly states the tool's function without any unnecessary words. It's perfectly front-loaded with the core action and target.

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?

For a zero-parameter mutation tool with no annotations and no output schema, the description provides the basic purpose but lacks important behavioral context about what 'clearing all cached data' entails, potential impacts, or confirmation of completion. It's minimally adequate but has clear gaps in safety/effect disclosure.

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 with 100% schema description coverage, so the schema already fully documents the lack of parameters. The description appropriately doesn't add parameter information beyond what's in the schema, maintaining the baseline for zero-parameter tools.

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 action ('초기화합니다' - initializes/clears) and the target ('캐시된 데이터' - cached data), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools, which appear to be read-only data retrieval functions, so this distinction is implied but not explicit.

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 or any prerequisites. While sibling tools are all 'get' operations (suggesting this is the only mutation tool), this isn't explicitly stated in the description itself.

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