Skip to main content
Glama
isnow890

Naver Search MCP Server

search_academic

Search scholarly articles and academic resources on Naver using customizable parameters like query, sort method, and result display settings.

Instructions

Perform a search on Naver Academic. (네이버 전문자료 검색)

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

  • Core handler function that executes the search_academic tool by parsing arguments and calling the Naver academic search client method.
    /**
     * 전문자료 검색 핸들러
     */
    export async function handleAcademicSearch(params: SearchArgs) {
      return client.searchAcademic(params);
    }
  • src/index.ts:222-235 (registration)
    MCP server registration of the search_academic tool, including description, input schema, and invocation of the handler.
    server.registerTool(
      "search_academic",
      {
        description:
          "🎓 Search academic papers, research documents, and scholarly content. Access Korean academic resources, research papers, theses, and professional publications. For recent publications or current research, use get_current_korean_time first. (네이버 전문자료 검색 - 학술 논문과 전문 자료, 최근 발표나 현재 연구를 찾을 때는 먼저 get_current_korean_time으로 현재 시간을 확인하세요)",
        inputSchema: SearchArgsSchema.shape,
      },
      async (args) => {
        const result = await searchToolHandlers.search_academic(args);
        return {
          content: [{ type: "text", text: JSON.stringify(result, null, 2) }],
        };
      }
    );
  • Zod input schema used for validating arguments to the search_academic tool.
    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: 날짜순)"),
    });
  • Client helper method that makes the HTTP GET request to Naver's academic document search API endpoint (/doc).
    /**
     * 전문자료 검색 메서드
     */
    async searchAcademic(
      params: NaverDocumentSearchParams
    ): Promise<NaverDocumentSearchResponse> {
      return this.get(`${this.searchBaseUrl}/doc`, params);
    }
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 offers minimal behavioral insight. It states it performs a search but doesn't disclose rate limits, authentication needs, pagination behavior, error conditions, or what the search results look like. For a search tool with zero annotation coverage, this is inadequate.

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 two brief phrases, front-loading the core purpose. Every word earns its place, and there's no redundant or verbose language. The Korean translation adds precision without bloating the text.

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 and no output schema, the description is incomplete for a search tool with 4 parameters. It doesn't explain what results to expect, how they're structured, or important behavioral aspects like rate limits or error handling. The high schema coverage helps but doesn't compensate for missing output and behavioral context.

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%, providing good documentation for all parameters. The description adds no parameter-specific information beyond what's in the schema, so it meets the baseline of 3 without compensating value. The Korean text doesn't clarify parameters further.

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 ('Perform a search') and target resource ('on Naver Academic'), with the Korean translation adding specificity. It distinguishes this tool from most siblings (e.g., search_blog, search_news) by specifying the academic domain, though it doesn't explicitly differentiate from all possible search tools.

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 when academic searches are appropriate compared to other search tools (like search_webkr or search_news) or the datalab_* tools, leaving the agent to infer usage context.

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