Skip to main content
Glama
isnow890

Naver Search MCP Server

search_encyc

Query Naver Encyclopedia to retrieve detailed information on specific topics. Customize results by adjusting display count, sorting by relevance or date, and specifying the start position.

Instructions

Perform a search on Naver Encyclopedia. (네이버 지식백과 검색)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
displayNoNumber of results to display (default: 10)
queryYesSearch query
sortNoSort method (sim: similarity, date: date)
startNoStart position of search results (default: 1)

Implementation Reference

  • The dispatcher handler for search_encyc tool that logs args, parses with schema, and calls the core search function.
    search_encyc: (args) => {
      console.error("search_encyc called with args:", JSON.stringify(args, null, 2));
      return handleEncycSearch(SearchArgsSchema.parse(args));
    },
  • Zod schema defining input parameters for the search_encyc tool (query, display, start, sort).
    export const SearchArgsSchema = z.object({
      query: z.string().describe("검색어"),
      display: z.number().optional().describe("한 번에 가져올 결과 수 (기본 10)"),
      start: z.number().optional().describe("검색 시작 위치 (기본 1)"),
      sort: z
        .enum(["sim", "date"])
        .optional()
        .describe("정렬 방식 (sim: 유사도, date: 날짜순)"),
    });
  • src/index.ts:207-219 (registration)
    MCP server registration for the search_encyc tool, specifying name, description, input schema, and wrapper handler.
    server.registerTool(
      "search_encyc",
      {
        description:
          "📖 Search Naver Encyclopedia for authoritative knowledge and definitions. Best for academic research, getting reliable information, and understanding Korean concepts and terminology. For current definitions or recent updates, use get_current_korean_time for context. (네이버 지식백과 검색 - 신뢰할 수 있는 정보와 정의, 현재 정의나 최근 업데이트를 찾을 때는 get_current_korean_time으로 상황을 파악하세요)",
        inputSchema: SearchArgsSchema.shape,
      },
      async (args) => {
        const result = await searchToolHandlers.search_encyc(args);
        return {
          content: [{ type: "text", text: JSON.stringify(result, null, 2) }],
        };
      }
  • Core helper function that executes the Naver encyclopedia ('encyc') search via the NaverSearchClient instance.
    export async function handleEncycSearch(params: SearchArgs) {
      return client.search("encyc", params);
    }
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. It mentions 'Perform a search' but doesn't disclose behavioral traits like rate limits, authentication needs, pagination behavior, error handling, or what the search returns. For a search tool with no annotation coverage, this leaves significant gaps in understanding how it behaves.

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 extremely concise with just one sentence plus a Korean translation, which is front-loaded and wastes no words. Every part earns its place by clearly stating the purpose without redundancy.

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 no annotations, no output schema, and a search tool with potential complexity (e.g., result format, limitations), the description is incomplete. It doesn't explain what the tool returns, any constraints, or how to interpret results, leaving the agent with insufficient context for effective use.

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 100%, so the schema fully documents all parameters. The description adds no additional parameter semantics beyond what's in the schema, such as explaining the search scope or result format. Baseline 3 is appropriate when the schema does the heavy lifting.

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 verb ('Perform a search') and resource ('on Naver Encyclopedia'), making the purpose explicit. It distinguishes from siblings by specifying the encyclopedia domain, though it doesn't explicitly contrast with other search tools like search_blog or search_news beyond the resource name.

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. With many sibling search tools (e.g., search_blog, search_news, search_academic), there is no indication of when encyclopedia searches are appropriate or what distinguishes this from other search types.

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

Related 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/isnow890/naver-search-mcp'

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