Skip to main content
Glama
Sign In
Pavo 官网 MCP

Pavo 官网 MCP

by congliu1851-ui
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

上传TXT或DOCX剧本

pavo_script_upload_file
Idempotent

Upload a local non-empty UTF-8 TXT or real DOCX to validate it and return file_url plus SHA for later AI episode planning. Use it before importing a script; limits: 32 MiB file, 64 MiB unzipped.

Instructions

准备步骤：上传本地非空UTF-8 TXT或真实DOCX并检查，返回file_url和SHA；文件32MiB、解压64MiB上限，不自动创建剧本。后续用import_file及计划集数交给Pavo AI生成分集；保留本地源文件用于核SHA及读取剧情。不发送Bearer到存储，inspect按用户文件上传授权调用。

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": {
      "path": "<path>",
      "operation_id": "<operation_id>"
    },
    "name": "pavo_script_upload_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
operation_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A3.9/5.0
Behavior4/5

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

Adds concrete behavior beyond the annotations: validation of non-empty UTF-8 input, 32MiB file and 64MiB decompressed limits, return of file_url and SHA, no Bearer token forwarded to storage, and authorization scoped to user file upload. Annotations only cover safety/idempotency, so this operational detail is genuine added value; only failure/error behavior is left unstated.

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?

Front-loads the preparation-step framing and packs limits, return values, and follow-up routing into a few dense clauses without filler. It is a single semicolon-chained block rather than clearly separated statements, which costs a little readability.

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?

An output schema exists, so the callout of file_url and SHA is a bonus rather than a necessity, and the operational constraints are well covered. What is missing is any explanation of path and operation_id, which is the main thing an agent needs in order to actually invoke the tool correctly.

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 description coverage is 0%, so the description must carry the parameter burden, but it only loosely implies that a local file path is 'uploaded' and never explains the required operation_id at all. Two required parameters with no documented meaning is a significant gap.

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 (upload a local UTF-8 TXT or real DOCX script file) and explicitly says it does not create a script, which cleanly separates it from pavo_script_import_file and pavo_script_create_ai.

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?

Frames itself as a preparation step and names the follow-on call (import_file with planned episode count) so the sequencing is unambiguous. It does not, however, state when to prefer this over the inline-text sibling pavo_script_import_text, leaving one routing decision to inference.

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