Skip to main content
Glama
Tech-curator

Korean Patent MCP

by Tech-curator

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
KIPRIS_API_KEYYesYour KIPRIS Plus Open API key (obtain from https://plus.kipris.or.kr)

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
kipris_search_patentsB

출원인명으로 한국 특허를 검색합니다.

Args:
    applicant_name: 출원인명 (필수, 예: '삼성전자', '카카오뱅크')
    page: 페이지 번호 (기본값: 1)
    page_size: 페이지당 결과 수 (기본값: 20, 최대: 100)
    status: 상태 필터 ('A': 공개, 'R': 등록, 'J': 거절, None: 전체)
    response_format: 응답 형식 ('markdown' 또는 'json')
kipris_get_patent_detailC

출원번호로 특허의 상세 정보를 조회합니다.

Args:
    application_number: 출원번호 (필수, 예: '1020200123456')
    response_format: 응답 형식 ('markdown' 또는 'json')
kipris_get_citing_patentsC

특정 특허를 인용한 후행 특허들을 조회합니다.

Args:
    application_number: 기준 특허의 출원번호 (필수)
    response_format: 응답 형식 ('markdown' 또는 'json')

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.2/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a clearly distinct purpose with no overlap: one retrieves patents citing a specific patent, another gets detailed information for a single patent, and the third searches patents by applicant name. The descriptions clearly differentiate these functions, making tool selection unambiguous for an agent.

Naming Consistency5/5

All tool names follow a consistent 'kipris_verb_noun' pattern (kipris_get_citing_patents, kipris_get_patent_detail, kipris_search_patents). This uniform naming convention makes the tool set predictable and easy to understand, with no deviations in style or structure.

Tool Count3/5

With only 3 tools, the set feels thin for a patent domain that typically involves more operations like updating, deleting, or analyzing patents. While the tools cover basic retrieval and search, the count is borderline low for comprehensive patent management, limiting agent capabilities.

Completeness2/5

The tool surface has significant gaps for a patent server, lacking essential operations such as creating, updating, or deleting patents, as well as advanced features like patent analysis or filtering by other criteria. This incompleteness will likely cause agent failures in handling full patent workflows.

Maintenance

ActivityInactive
ResponsivenessNo issues