Skip to main content
Glama

get_movie_chart

Read-only

Fetch Douban movie charts for Top 250, weekly word-of-mouth, or recent releases, with pagination controls to browse ranked films.

Instructions

获取电影榜单。kind: top250 (Top250)、weekly (一周口碑榜)、new (近期上映)。

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": {
      "kind": "<kind>"
    },
    "name": "get_movie_chart"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
countNo
startNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.0.1
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / start / maximum
      Added value: +9007199254740991
  2. First observedv1.0.0-alpha.0

TDQS

B3.3/5.0
Behavior2/5

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

The readOnlyHint=true annotation already declares the safe-read profile. Beyond that the description adds nothing behavioral: no indication of ordering, whether the list is paginated, response shape, or rate limits, even though the start/count parameters imply paging.

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 compact sentences, front-loaded with the verb and resource, then the parameter value legend. No filler whatsoever.

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

Completeness3/5

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

With three parameters, a required enum, and no output schema, the description covers the essential selection input but leaves pagination behavior and the shape of a chart entry unexplained. Adequate to invoke, incomplete for interpreting results.

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 must compensate. It does explain the meaning of each kind value beyond the bare enum, but count and start (defaults 10/0, max 25) are left entirely undocumented, so coverage is only partial.

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 (获取电影榜单) and enumerates all three chart kinds with glosses, so an agent can distinguish it from siblings such as get_book_chart or get_movie. It does not explicitly name what it is not, which keeps it just short of a 5.

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 implied: an agent can infer this is for browsing ranked movie lists, and the kind glosses hint at the different scenarios. There is no explicit when-to-use vs alternatives guidance (e.g., versus search_movie or get_movie) and no exclusions.

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