Skip to main content
Glama
Sign In
kobis-mcp

kobis-mcp

by myungwoon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Get Daily Box Office

get_daily_box_office
Read-onlyIdempotent

Retrieve daily box office rankings by date, including audience counts, revenue, and cumulative admissions, with filters for nation, region, and movie type. Defaults to yesterday (KST).

Instructions

일별 박스오피스 순위(관객수, 매출액, 누적관객 등)를 조회합니다. 기본값은 어제(KST)입니다. 오늘 이후 날짜는 집계되지 않습니다.

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

Input Schema

NameRequiredDescriptionDefault
itemsNo결과 수 (1~10)
nationNoall 전체 / korean 한국영화 / foreign 외국영화all
area_codeNo광역지역 코드 (예: 0105001 서울). get_code_list('0105000000') 로 조회
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.9/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive). The description adds real data-freshness context — default of yesterday KST and that today-or-later is unavailable — which is genuinely beyond the annotations, but nothing is said about pagination limits or ordering beyond rank.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with purpose, then default value, then the one non-obvious limit. No filler or redundancy.

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?

All five parameters are optional, an output schema exists, and annotations are rich, so the description only needs purpose plus edge behavior — both present. The gap is the absence of any statement about how this relates to the weekly variant or the max-10 result cap.

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

Parameters4/5

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

Schema coverage is 100% so the baseline is 3, but the description adds a substantive constraint absent from the schema: dates after today are not aggregated, which meaningfully informs target_date usage. The remaining parameters (items, nation, area_code, movie_type) are left entirely to 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 (조회합니다) and resource (일별 박스오피스 순위) and even enumerates returned fields (관객수, 매출액, 누적관객). It does not explicitly distinguish itself from the sibling get_weekly_box_office, so the daily-vs-weekly split is left to name inference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It clearly states the default date behavior (기본값은 어제, KST) and a practical constraint that future dates are not yet aggregated, which tells an agent when the call will succeed. It gives no explicit exclusions or routing to the weekly sibling.

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