Skip to main content
Glama
KOBIS MCP Server

KOBIS MCP Server

by una4199

KOBIS 영화사 검색

kobis_search_companies
Read-onlyIdempotent

Search film companies by company name or representative name to find matching Korean movie production and distribution companies.

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

Input Schema

NameRequiredDescriptionDefault
ceoNmNo대표자명
curPageNo페이지 번호, 기본값 1
companyNmNo영화사명
itemPerPageNo페이지당 결과 수, 기본값 10, 최대 100

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 readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds nothing behavioral beyond that — no mention of multiple results, empty-result behavior, pagination, or partial-match semantics — so it essentially restates the title.

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 or repetition. It is efficient, though the brevity edges toward under-specification rather than optimal density.

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?

All four parameters are optional and fully described by the schema, and annotations cover the safety profile, so the basics are present. Still, for a search tool an agent would benefit from knowing result-matching behavior and whether paging is needed, which the description omits.

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 coverage is 100%, so companyNm, ceoNm, curPage and itemPerPage are already documented. The description confirms the two name parameters are the intended search keys but adds no matching rules, such as whether matching is exact or partial, so it stays at the baseline.

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 (검색합니다) and resource (영화사) and names the two search keys, 영화사명 and 대표자명. This is clear enough to distinguish it from a details-lookup tool, but it never references the sibling name-search tools (kobis_search_movies, kobis_search_people) or kobis_company_details.

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 or when-not-to-use guidance, and no alternative is named. At best the mention of two search keys implies 'use this when you have a company name or CEO name,' which is only implicit usage framing.

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