Skip to main content
Glama
jikime

Naver Search MCP Server

search_encyclopedia

Find encyclopedia information on Naver by entering keywords, with options to navigate pages and sort results for comprehensive research.

Instructions

Searches for encyclopedia information on Naver using the given keyword. The page parameter allows for page navigation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
displayNo
pageNo
sortNosim

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • server.py:434-437 (registration)
    MCP tool decorator registering the 'search_encyclopedia' tool with its description.
    @mcp.tool(
      name="search_encyclopedia",
      description="Searches for encyclopedia information on Naver using the given keyword. The page parameter allows for page navigation."
    )
  • The handler function for the search_encyclopedia tool. It calculates pagination parameters, prepares the API request params, and delegates to the shared _make_api_call helper function for the Naver encyclopedia ('encyc.json') endpoint.
    async def search_encyclopedia(query: str, display: int = 10, page: int = 1, sort: str = "sim") -> str:
        """
        Searches for encyclopedia information on Naver using the given keyword. The page parameter allows for page navigation.
    
        Args:
            query (str): The keyword to search for
            display (int, optional): The number of results to display. Default is 10.
            page (int, optional): The starting page number. Default is 1.
            sort (str, optional): The sorting criteria. Default is "sim" (similarity).
        """
        start = calculate_start(page, display)
        display = min(display, 100)
        params = {"query": query, "display": display, "start": start, "sort": sort}
        return await _make_api_call("encyc.json", params, EncycResult, "Encyclopedia")
  • Pydantic schema for individual encyclopedia search result items.
    class EncycItem(BaseItem):
        thumbnail: Optional[str] = None
        description: Optional[str] = None
  • Pydantic schema for the full encyclopedia search API response.
    class EncycResult(SearchResultBase): items: List[EncycItem]
  • Helper function used by search_encyclopedia (and other tools) to compute the 'start' pagination parameter for Naver API calls.
    def calculate_start(page: int, display: int) -> int:
        """Calculates the start value for the API call based on the page number and display count."""
        if page < 1:
            page = 1
        start = (page - 1) * display + 1
        # 네이버 API의 start 최대값(1000) 제한 고려
        return min(start, 1000)
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 mentions page navigation. It lacks critical behavioral details such as rate limits, authentication needs, result format, or whether it's read-only. This leaves significant gaps in understanding how the tool behaves beyond basic functionality.

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 concise with two sentences, front-loading the main purpose. However, the second sentence about page navigation could be integrated more smoothly, and it lacks efficiency by not covering other parameters or usage context.

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 4 parameters with 0% schema coverage, no annotations, but an output schema exists, the description is incomplete. It doesn't explain parameter meanings or behavioral traits, though the output schema may cover return values. This results in a minimally adequate but gap-filled description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It only explains the 'page' parameter ('allows for page navigation'), ignoring 'query', 'display', and 'sort'. This adds minimal value beyond the schema, failing to fully address the coverage gap, warranting a baseline score.

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 ('Searches for encyclopedia information') and the target resource ('on Naver'), distinguishing it from siblings like search_blog or search_news. However, it doesn't specify the exact scope of 'encyclopedia information' (e.g., entries, articles) or differentiate from similar tools like search_doc, which slightly reduces specificity.

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 like search_webkr or search_kin. It mentions page navigation but doesn't explain when to use this tool over other search tools, leaving the agent without context for selection among siblings.

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/jikime/py-mcp-naver-search'

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