Skip to main content
Glama

generate_drama_poster

Generate a promotional key visual poster for a whole drama using its ID. Solve artwork needs with usage-based, post-paid billing per image.

Instructions

给整部剧生成海报图(KV)。图片步,按用量后付。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
drama_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.57

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the disclosure burden. It adds one useful behavioral trait—'按用量后付' (billed by usage)—but says nothing about async behavior, return values, side effects, or prerequisites. The cryptic '图片步' phrase further weakens transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loaded with the main purpose, which is good. However, the second sentence is garbled ('图片步,按用量后付') and does not cleanly communicate its intended meaning, reducing overall clarity.

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

Completeness2/5

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

This tool has no output schema and no annotations, so the description should explain return behavior and any necessary preconditions. It does not mention what the agent receives after generation, whether the call is asynchronous, or whether the drama must already exist. The simple single-parameter schema prevents a lower score, but the gaps are material.

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?

Schema coverage is 0% and the description does not explain drama_id beyond the term '整部剧'. It omits how to obtain a valid drama_id, whether existing dramas are required, or any constraints beyond the integer type already in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific action ('生成海报图') with a clear resource ('KV poster') and scope ('整部剧'). This cleanly distinguishes it from sibling tools like generate_episode_poster and generate_cover.

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: the '整部剧' wording suggests it is for full-drama posters rather than episode or cover posters. However, it never explicitly names alternatives or states when to prefer this tool over generate_episode_poster or generate_cover.

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

Deploy Server

Other Tools