Skip to main content
Glama
Sign In
kobis-mcp

kobis-mcp

by myungwoon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Get Weekly Box Office

get_weekly_box_office
Read-onlyIdempotent

Retrieve weekly, weekend, or weekday Korean box office rankings by date, region, film type, and nation for performance analysis.

Instructions

주간/주말 박스오피스 순위를 조회합니다. target_date 가 속한 주의 결과를 돌려주며, 기본값은 지난주(오늘-7일)입니다.

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": "get_weekly_box_office"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsNo결과 수 (1~10)
nationNoall 전체 / korean 한국영화 / foreign 외국영화all
area_codeNo광역지역 코드
week_typeNoweekend 주말(금~일) / weekly 주간(월~일) / weekdays 주중(월~목)weekly
movie_typeNoall 전체 / diversity 다양성영화 / commercial 상업영화all
target_dateNo조회 날짜. YYYYMMDD 또는 YYYY-MM-DD. 생략하면 기본값 사용

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/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 covered. The description adds genuinely new behavior: the result set is the week containing target_date, and omitting the date defaults to last week (today-7). It says nothing about return shape, ordering, or data-recency limits, which keeps it at a middling score.

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?

Two compact sentences, front-loaded with the core purpose and followed by the scoping rule and default. No filler, though it is arguably too terse for a six-parameter tool with three enum dimensions.

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

Completeness4/5

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

An output schema exists, so return values need not be explained, and all six parameters are fully described in the schema with defaults and enums. The remaining omission is routing guidance versus the daily box office sibling, which is a modest gap rather than a blocking one.

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%, so every parameter including the three enums is already documented in the schema, making 3 the baseline. The description adds only the default value of target_date, a small increment over the schema's "생략하면 기본값 사용".

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 weekly/weekend box office rankings) and implies the weekly aggregation scope, which distinguishes it in substance from get_daily_box_office. It does not name the daily sibling explicitly, so the differentiation is implicit rather than stated.

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?

"target_date 가 속한 주의 결과를 돌려주며" clarifies which week's results are returned, which is a meaningful usage hint, and the default (today-7) is given. However, there is no explicit guidance on when to choose this over get_daily_box_office, nor any stated prerequisites or exclusions.

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

Deploy Server

Other Tools