Skip to main content
Glama

Search Movies

search_movies
Read-onlyIdempotent

Find Korean films by title, director, release or production year, nationality, or type; returned movie_cd values let you retrieve detailed movie information.

Instructions

영화를 검색합니다 (영화명·감독·개봉/제작연도·국적·유형). 결과의 movie_cd 로 get_movie_info 를 호출할 수 있습니다.

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

Input Schema

NameRequiredDescriptionDefault
pageNo페이지 번호 (1부터)
per_pageNo페이지당 결과 수 (최대 100)
movie_nameNo영화명 (부분 일치)
nation_codeNo대표 국적 코드 (예: 22041011 한국). get_code_list('2204') 로 조회
director_nameNo감독명
open_end_yearNo개봉연도 끝 (YYYY)
open_start_yearNo개봉연도 시작 (YYYY)
movie_type_codesNo영화유형 코드, 쉼표로 여러 개 (예: 220101). get_code_list('2201') 로 조회
production_end_yearNo제작연도 끝 (YYYY)
production_start_yearNo제작연도 시작 (YYYY)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/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 fully covered elsewhere. The description contributes the result-to-lookup linkage (movie_cd), which is useful behavior context. It says nothing about pagination limits, empty-result behavior, or result volume, which is a gap but a modest one given the annotation coverage.

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?

Two sentences, no waste: the searchable scope is front-loaded and the chaining hint trails it. Nothing is repeated from structured fields verbatim and nothing could be cut without losing information.

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 parameters are optional, an output schema exists, and annotations cover the side-effect profile, so the description only needed to state scope and the natural follow-up call — both are present. It falls just short of full completeness because a 10-parameter search tool could note how filters combine (AND vs OR) or that unfiltered calls are permitted.

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%: every one of the 10 parameters is documented in the schema, including code lookups via get_code_list and the comma-separated multi-code convention. The description merely summarizes the same field families at a higher level, adding no syntax or format detail beyond the schema. Baseline 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?

"영화를 검색합니다" gives a specific verb plus resource, and the parenthetical enumerates the searchable axes (title, director, release/production year, nationality, type). The resource noun alone separates it from search_people / search_companies, though it never names a sibling explicitly.

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?

The second sentence supplies clear usage context for the follow-up step: take movie_cd from the results and pass it to get_movie_info. That is a real workflow instruction rather than filler. It stops short of a 5 because there is no when-not guidance or explicit alternative (e.g., when to search people/companies instead).

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