Skip to main content
Glama

AutoTasker Hub — China Social Data API

douban_movie

Douban "now showing" cinema board: titles, cast, genres, release dates, ratings (豆瓣热映). $0.02 USDC.

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

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does add two genuinely useful behavioural facts: the exact fields returned (titles, cast, genres, release dates, ratings) and the per-call cost of $0.02 USDC, which matters for an agent budgeting calls. It says nothing about the source's rate limits, whether the board is region-locked, how fresh the data is, or what happens on error.

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?

A single front-loaded sentence with the resource and payload listed before the parenthetical alias and the price. Nothing is redundant, though the price tag sits at the end where it could be overlooked, and no structure separates the payload list from the cost note.

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 no output schema and no annotations, the description must cover both payload and behaviour. It does list the returned fields, which is the right instinct, but for a paid tool it omits the limit parameter's meaning, result count behaviour, and any freshness or failure semantics, leaving real gaps for a one-parameter feed tool.

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

Parameters2/5

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

There is a single optional parameter, limit, and the schema gives only a default of 10 and a maximum of 20 with zero description coverage. The description never mentions the parameter at all, so an agent gets no explanation of what the limit caps (number of films) or that 20 is a hard ceiling. One obvious parameter keeps this from the bottom of the scale.

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 resource (the Douban "now showing" cinema board, 豆瓣热映) and enumerates the data it returns: titles, cast, genres, release dates, ratings. That is far more specific than the tool name alone, which could be mistaken for a general movie search. It does not, however, distinguish itself from any sibling or state that it is scoped to currently-in-theatres rather than a general catalogue search, so it stops 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 only implied: an agent can infer this is the tool for current cinema listings, and the parenthetical 豆瓣热映 confirms the Chinese-market scope. There is no explicit when-to-use or when-not-to-use statement, no mention of what it does not cover (e.g. historical or streaming titles), and no named alternative among the siblings.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.