Skip to main content
Glama
KOBIS MCP Server

KOBIS MCP Server

by una4199

KOBIS 주간/주말 박스오피스

kobis_weekly_box_office
Read-onlyIdempotent

Query weekly, weekend, or weekday box office rankings for the week containing a given date, filtered by region, nation, or movie type.

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

Input Schema

NameRequiredDescriptionDefault
weekGbNo0=주간, 1=주말, 2=주중; 기본값 0
targetDtYes조회 기준 날짜(YYYYMMDD)
wideAreaCdNo
itemPerPageNo
repNationCdNo
multiMovieYnNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/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 and destructiveHint=false, so the safety profile is covered. The description adds genuine behavioral context: the query date selects an entire week, and results can be segmented by week/weekend/weekday. It says nothing about pagination, result size, or what happens for dates at week boundaries.

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 that names the scope before anything else, with no filler. It is efficiently sized, though its brevity is part of why the parameter and behavioral gaps remain.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 6-parameter tool with no output schema and only 33% schema description coverage, the description is too thin. An agent gets no help on filtering parameters (nation, multi-movie, wide area) or pagination, which are exactly the gaps structured fields leave open.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33%, so the description must compensate for the four undocumented parameters. It only implicitly touches targetDt and weekGb (whose enum the schema already documents); wideAreaCd, repNationCd, multiMovieYn and itemPerPage receive no explanation in either place.

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 a clearly scoped resource (주간·주말·주중 박스오피스 순위 for the week containing the given date). The word '주간' implicitly separates it from the daily sibling kobis_daily_box_office, but it never names that sibling or states the distinction 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 implied by the resource statement: an agent can infer this is the tool for week-level rankings rather than daily ones. However, there is no explicit when-to-use guidance, no mention of when the daily tool would be preferred, and no guidance on how the weekGb mode should be chosen for a given question.

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