Skip to main content
Glama
KOBIS MCP Server

KOBIS MCP Server

by una4199

KOBIS 영화인 검색

kobis_search_people
Read-onlyIdempotent

Search film people by name or by a movie title they participated in, with pagination controls for browsing matching results.

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_people"
  }
}

Input Schema

NameRequiredDescriptionDefault
curPageNo페이지 번호, 기본값 1
peopleNmNo영화인 이름
filmoNamesNo참여 영화명
itemPerPageNo페이지당 결과 수, 기본값 10, 최대 100

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds only the search-mode context and says nothing about paging behavior or how many results a query may return, so it does not enrich behavior beyond the annotations.

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 front-loaded sentence with no filler, which suits a four-parameter search tool. It is efficient but so terse that it leaves the two filter names as the only content, with no structuring of what happens when both are supplied.

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 tool is simple, has no output schema, and has fully documented parameters plus rich annotations, so little is strictly required. Still, an agent gets no statement about combining peopleNm with filmoNames, about empty results, or about pagination, leaving gaps that the description could have closed cheaply.

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%, with curPage, peopleNm, filmoNames and itemPerPage all documented in the schema including defaults and the 100 cap. The description merely restates the two name-based filters and adds no semantics (matching rules, partial-match behavior, combined-filter behavior) beyond the schema.

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 names a specific verb (검색합니다) and resource (영화인), and states the two search keys (이름, 참여 영화명), so an agent can distinguish it from kobis_search_movies or kobis_search_companies. It stops short of explicitly contrasting itself with kobis_person_details, which is the closest sibling by subject matter.

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 two search criteria imply when the tool is applicable (when you have a person name or a film title but not an ID), but the description never states when to prefer this over kobis_person_details or what to do if multiple matches come back. Usage is inferable rather than spelled out.

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