Skip to main content
Glama

Get Movie Info

get_movie_info
Read-onlyIdempotent

Retrieve detailed Korean movie information—runtime, release date, genre, director, cast, rating, and production/distributor—by passing a movie code from search results.

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": {
      "movie_cd": "<movie_cd>"
    },
    "name": "get_movie_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
movie_cdYes영화 코드 (search_movies 결과의 movie_cd)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so safety and idempotency are covered. The description adds the set of fields the lookup surfaces, which is useful context, but nothing about failure modes for invalid/unknown movie codes or about the response shape beyond the field list, and an output schema already exists.

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?

One compact sentence that front-loads the core purpose and then parenthetically enumerates returned fields; nothing is redundant or padded. It could be improved only by spending a few of those words on when to use it.

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

Completeness5/5

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

For a simple one-parameter read tool with full annotation coverage, complete schema documentation, and an output schema, the definition is adequate as written. Nothing needed to invoke it correctly is missing.

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?

There is a single parameter with 100% schema description coverage, so the schema already explains movie_cd as the movie code from search_movies results. The description adds no further meaning, and the baseline of 3 applies when the schema does the work.

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 gives a specific verb plus resource (영화 상세 정보 … 조회) and enumerates the returned attributes (runtime, release date, genre, director, cast, rating, studios), so an agent can tell this is a detail-fetch tool. It does not differentiate itself from the sibling search_movies, even though the schema's own parameter description depends on search_movies output.

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?

The description says only that it retrieves details; it never states when to use this instead of search_movies or the box-office siblings, nor that a movie_cd must first come from a search. The only workflow hint (search_movies 결과의 movie_cd) lives in the schema, not the description.

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