Skip to main content
Glama
KOBIS MCP Server

KOBIS MCP Server

by una4199

KOBIS 영화 상세정보

kobis_movie_details
Read-onlyIdempotent

Fetch detailed movie information using a KOBIS movie code to view title, release date, genre, and related metadata.

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": {
      "movieCd": "<movieCd>"
    },
    "name": "kobis_movie_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
movieCdYesKOBIS 영화 코드

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, destructiveHint=false and openWorldHint, so the safety profile is covered by structured data. The description adds only that lookup is keyed by code; it says nothing about what happens with an invalid or expired code, response language, or which detail fields are returned.

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 short sentence with the lookup key front-loaded and no filler or repetition. It is efficient, though it is terse to the point that useful context is omitted rather than compressed.

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 one-parameter lookup with no output schema and full annotation coverage, the description is minimally sufficient to invoke the tool correctly. It is incomplete on the return payload and on error conditions, which an agent would need for a required string code query against an external API.

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% and the single parameter movieCd carries its own description ('KOBIS 영화 코드'), so the schema does the heavy lifting. The description repeats the same idea ('영화 코드로') without adding format, length, or validity constraints, so baseline 3 applies.

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 uses a specific verb (조회합니다) plus a clear resource (영화의 상세정보) and states the lookup key (KOBIS 영화 코드), so an agent can tell it retrieves movie detail rather than performing a search. It does not name a sibling to contrast with, which keeps it short of a 5.

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 phrase '영화 코드로' implies this tool is for when a KOBIS movie code is already known, but it never says so explicitly or points to kobis_search_movies for obtaining a code. Usage must be inferred from the required parameter.

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