Skip to main content
Glama
KOBIS MCP Server

KOBIS MCP Server

by una4199

KOBIS 영화인 상세정보

kobis_person_details
Read-onlyIdempotent

Fetch a film person's details and filmography by KOBIS person code to look up profile and credit information from the KOBIS movie database.

Instructions

KOBIS 영화인 코드로 상세정보와 필모그래피를 조회합니다.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "peopleCd": "<peopleCd>"
    },
    "name": "kobis_person_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
peopleCdYesKOBIS 영화인 코드

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 readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description contributes only that filmography is included in the response; it says nothing about behavior for unknown codes, error shape, or result size.

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?

One front-loaded sentence with the key stated before the outcome and no filler. It is close to the minimum useful length, though it could spend one more clause on the response contents or prerequisite.

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?

For a single-parameter read tool with full annotation coverage and no output schema, the description is minimally sufficient: it states input key and that details plus filmography are returned. It stops short of covering how to obtain a valid code or what happens on an invalid one.

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?

There is a single parameter with 100% schema description coverage, so the schema already defines peopleCd. The description reinforces that it is the KOBIS person code used as the lookup key but adds no format, example, or source-hint (e.g. where to obtain the code) 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 lookup key (KOBIS 영화인 코드). An agent can distinguish it from kobis_search_people by the fact that it takes an identifier rather than a query, though no sibling is named explicitly.

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?

Usage is only implied: it presumes the caller already holds a KOBIS person code, which suggests search_people is the discovery path, but the description never says so or states any when-not condition. Adequate for a straightforward detail lookup, but the routing guidance is left to inference.

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