Skip to main content
Glama
KOBIS MCP Server

KOBIS MCP Server

by una4199

KOBIS 영화 검색

kobis_search_movies
Read-onlyIdempotent

Search Korean movie records by title, director, production year, release date, country, or type to retrieve matching film data.

Instructions

영화명, 감독명, 제작연도, 개봉일 등의 조건으로 영화를 검색합니다.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "kobis_search_movies"
  }
}

Input Schema

NameRequiredDescriptionDefault
curPageNo페이지 번호, 기본값 1
movieNmNo영화명
openEndDtNo개봉일 종료(YYYYMMDD)
directorNmNo감독명
itemPerPageNo페이지당 결과 수, 기본값 10, 최대 100
movieTypeCdNo영화 유형 코드
openStartDtNo개봉일 시작(YYYYMMDD)
prdtEndYearNo
repNationCdNo대표 국가 코드
prdtStartYearNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so safety needs no restating. The description adds nothing behavioral beyond that: no indication of pagination behavior, default result count, empty-result handling, or the fact that the filters are combined as AND conditions.

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?

A single sentence that front-loads the resource and lists the filters, with no filler. It is efficient but arguably too terse given ten parameters, so it stops just short of ideal structure.

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?

With ten optional parameters, pagination controls (curPage, itemPerPage up to 100), and no output schema, the description should explain that all filters are optional, how paging works, and what a result contains. None of that is covered, so an agent must reconstruct calling behavior entirely from the schema.

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 80%, so the baseline is 3. The description echoes four filter names (movie name, director, production year, release date) already documented in the schema, and lightly implies that production year is a range via prdtStartYear/prdtEndYear, which lack schema descriptions. It does not clarify the optional nature of every parameter or the page-number parameters.

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 states a specific verb (검색합니다) plus resource (영화) and enumerates the filter dimensions (영화명, 감독명, 제작연도, 개봉일). An agent can tell this is a search/list tool as opposed to the detail siblings, though the distinction is inferred from the name rather than stated.

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?

There is no when-to-use guidance, no mention of when this tool should not be used instead of kobis_movie_details, and no note that all filters are optional or how results should be narrowed. The only hint is the word 'search' plus the filter list, leaving the agent to infer the search-vs-details routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.