Skip to main content
Glama
KOBIS MCP Server

KOBIS MCP Server

by una4199

KOBIS 일별 박스오피스

kobis_daily_box_office
Read-onlyIdempotent

Fetch Korean daily box office rankings for a specific date and apply filters by region, film type, or variety film status.

Instructions

특정 날짜의 한국 영화관 일별 박스오피스 순위를 조회합니다.

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": {
      "targetDt": "<targetDt>"
    },
    "name": "kobis_daily_box_office"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetDtYes조회 날짜(YYYYMMDD), 보통 전날 날짜
wideAreaCdNo광역 지역 코드
itemPerPageNo
repNationCdNo한국/외국 영화 구분
multiMovieYnNo다양성 영화 여부

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?

The annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is clear. The description does not contradict them, but it adds no further behavioral context such as authentication needs, rate limits, result ordering, or pagination behavior.

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?

The description is a single well-formed sentence with no filler and the core purpose is front-loaded. It is appropriately sized, though its brevity also reflects the missing usage guidance and return-value context.

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 schema and annotations cover most structural and safety details for this five-parameter query tool. However, the description does not explain the expected ranking results, does not mention the weekly alternative, and does not address pagination despite the itemPerPage parameter.

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 80%, so most parameters are already documented in the schema, including the required targetDt with its YYYYMMDD pattern and the note that it is usually the previous day. The description adds no parameter meaning beyond what the schema provides, so the baseline of 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 states a specific verb and resource: 조회 (retrieve) the daily box office rankings for Korean cinemas on a specific date. The word 일별 (daily) distinguishes it from the sibling kobis_weekly_box_office, but the description does not explicitly name or contrast that alternative.

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?

It gives no when-to-use or when-not guidance. It does not mention when to choose this daily tool over kobis_weekly_box_office, nor does it explain when optional filters like region, nationality, or diversity should be applied.

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