Skip to main content
Glama
KOBIS MCP Server

KOBIS MCP Server

by una4199

KOBIS 영화사 상세정보

kobis_company_details
Read-onlyIdempotent

Retrieve detailed information and related movies for a Korean film company using its KOBIS company code. Use this to identify a company and explore its associated film titles.

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": {
      "companyCd": "<companyCd>"
    },
    "name": "kobis_company_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyCdYesKOBIS 영화사 코드

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered structurally. The description adds only one behavioral fact beyond that — that results include related films (관련 영화) — but says nothing about result size, missing-code behavior, or external API failure modes.

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 zero filler, and the keying parameter is stated first. It is efficient, though its brevity is also the source of the missing guidance rather than a deliberate compression of rich content.

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 read-only lookup the description is minimally sufficient, and with no output schema present the mention of 관련 영화 does part of the work of describing returns. However it never explains how to obtain a valid company code or what the response shape/coverage looks like, which an agent needs to chain calls correctly.

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 there is only one parameter, already documented as 'KOBIS 영화사 코드'. The phrase '영화사 코드로' merely restates that the lookup is keyed on the code; it adds no format, sourcing, or example detail 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 (조회합니다 / retrieve) and a specific resource (KOBIS 영화사 상세정보, plus 관련 영화), so the agent knows this looks up company details and associated films. It does not explicitly contrast itself with kobis_search_companies or kobis_company_details-style siblings, which keeps it out of 5 territory.

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 explicit when-to-use guidance: nothing says the caller must already hold a KOBIS company code (obtained from kobis_search_companies) rather than a company name. No alternatives or exclusions are mentioned, so routing between this and the search tools is left entirely to inference.

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