Skip to main content
Glama
Sign In
Pavo 官网 MCP

Pavo 官网 MCP

by congliu1851-ui
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

AI创作剧本

pavo_script_create_ai
Idempotent

Generates AI script plans for 1–100 episodes with chosen aspect ratio and style via one authorized request, returning project and task IDs without confirming outlines or starting media.

Instructions

调用官网AI剧本生成，可能消耗额度，需用户授权本次创作与费用。计划1至100集、画幅9:16或16:9，style使用实时style_id或custom_style_prompt。只提交一次并返回真实project_id/task_ids，不自动确认大纲或启动后续媒体。

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": {
      "requirements": "<requirements>",
      "planned_episode_count": "<planned_episode_count>",
      "ratio": "<ratio>",
      "style": "<style>",
      "operation_id": "<operation_id>"
    },
    "name": "pavo_script_create_ai"
  }
}

Input Schema

NameRequiredDescriptionDefault
ratioYes
styleYes
operation_idYes
requirementsYes
planned_episode_countYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing that credits may be consumed and that user consent for cost is needed, that the call should only be submitted once, that real project_id/task_ids are returned, and that no outline confirmation or downstream media is triggered. These are the exact behavioral traits an agent needs before firing an expensive generation.

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?

Dense but front-loaded, leading with the cost/authorization warning before the parameter constraints. Every clause carries information; the semicolon-chained constraint list is efficient though slightly compressed for readability.

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 5-required-parameter, nested-style, output-schema-backed generation tool, the description covers cost, authorization, constraints, return identifiers, and the deliberate absence of chained steps. The output schema handles return values, so no gap remains that would cause a wrong invocation.

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

Parameters4/5

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

With 0% schema description coverage, the description carries the load and does add meaning: episode count range 1–100, ratio constrained to 9:16 or 16:9, and style expecting a live style_id or a custom_style_prompt. It leaves 'requirements' and 'operation_id' unexplained, so one parameter and the idempotency key's role remain implicit.

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?

States a specific verb and resource: invoking the official-site AI script generation to create a script project. It distinguishes itself from siblings such as pavo_script_import_text, pavo_script_upload_file and pavo_script_run_stage by naming the generation action and the scope (episodes, ratio, style).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear context for use: requires user authorization for the creation and its cost, must be submitted exactly once, and explicitly does not auto-confirm the outline or kick off downstream media work. It does not name the follow-up tools (outline update / stage run) explicitly, so routing is implied rather than spelled out.

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