Skip to main content
Glama
iapke486-arch

kci-mcp-server

kci_get_journal_citations

Retrieve journal citation indices such as impact factor, immediacy index, and self-citation ratio for Korean academic journals based on a reference year and number of years.

Instructions

기준년도(year)와 포함년도(years)를 기준으로 저널(학술지)들의 인용지수(영향력 지수, 즉시성 지수, 자기인용 비율 등) 목록을 조회합니다.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
doiNoDOI
pageNo페이지 번호
yearYes기준년도 (YYYY, 필수)
yearsYes포함 년도 수 (2~5, 필수, 기본 2)
sortNmNo정렬 기준: title(제목), author(저자명), pubiYr(발행일자)
journalNo저널(학술지) 이름
sortDirNo정렬 방향: asc(오름차순), desc(내림차순)
modDateToNo수정일 끝 (YYYYMMDD)
institutionNo발행 기관명
modDateFromNo수정일 시작 (YYYYMMDD)
displayCountNo출력 건수 (기본 10, 최대 100)
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as read-only nature, side effects, or permissions. It only states what the tool retrieves, leaving behavior largely unspecified.

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 concise sentence in Korean. It front-loads the key parameters and purpose without any redundant or unclear phrasing.

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?

The description mentions examples of returned data but does not explain pagination, sorting, or other parameters' roles. For a tool with 11 parameters and no output schema, more detail would improve completeness.

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?

Schema description coverage is 100%, so baseline is 3. The description adds value by listing specific citation indices (영향력 지수, 즉시성 지수, 자기인용 비율 등) that are returned, which is beyond what input schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool retrieves citation indices (impact factor, immediacy index, self-citation rate) for journals based on year and years. It distinguishes from sibling tools which focus on article details, citation details, or search.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies use when needing journal citation indices by year range, but does not explicitly state when to use this tool versus alternatives or provide exclusions. No usage guidance beyond implied 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

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/iapke486-arch/mcp-server'

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