Skip to main content
Glama

get_movie

Read-only

Retrieve detailed Douban movie information—including director, cast, rating, and synopsis—by providing a numeric Douban subject ID.

Instructions

获取一部电影的详细信息(导演、演员、评分、简介等)。id 是豆瓣电影 subject id(数字)。

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": {
      "id": "<id>"
    },
    "name": "get_movie"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.1
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv1.0.0-alpha.0

TDQS

A3.5/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes this is a safe read, so the description only needs to add context. It discloses the returned field set (director, cast, rating, synopsis), which is genuinely useful, but says nothing about failure modes for invalid/nonexistent ids or about response shape beyond the field list.

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 short sentences, no filler, with the purpose front-loaded and the identifier clarification second. Efficient for the amount of information conveyed.

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?

For a single-parameter read tool with no output schema, the description covers purpose, the identifier's origin, and the fields returned, which is close to sufficient. A brief pointer to how to get the id would make it complete.

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 0%, so the description carries the burden and does partially meet it by explaining that id is a Douban movie subject id and is numeric, which goes beyond the bare digit-pattern in the schema. It does not say how to obtain that id (e.g., from search_movie), leaving the practical gap.

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 lists what the response contains (director, cast, rating, synopsis), so the agent can distinguish it from chart/reviews siblings at a glance. It stops short of naming which sibling to use instead, so it is clear but not explicitly differentiated.

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 only implied: the agent is expected to infer that this is the detail lookup once a subject id is known. There is no statement about when to prefer search_movie, nor any note that an id must first be obtained elsewhere, which is the key routing decision for this tool family.

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