Skip to main content
Glama
Sign In
Pavo 官网 MCP

Pavo 官网 MCP

by congliu1851-ui
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

读取剧本风格库

pavo_script_list_styles
Read-onlyIdempotent

Fetches the live style library for AI script creation and returns valid style IDs, helping you avoid using canvas templates or model codes as style IDs.

Instructions

读取独立AI剧本创作入口的实时风格库；使用真实style_id，不把画布模板或模型code当风格ID。

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds that the library is '实时' (real-time/live), which is useful behavioral context not in the annotations, but says nothing about caching, size, or ordering of results.

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?

Two short clauses with no wasted words; the purpose is front-loaded before the ID-correctness caveat. Slightly more structure (e.g., separating the guideline) would help, but it is tight as written.

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 an output schema present and no parameters, the description does not need to explain return values, and the read-only annotations cover safety. Still, for a tool whose whole job is feeding correct style IDs into script creation, it lacks context on how the returned styles relate to downstream tools like pavo_script_create_ai, leaving a modest gap.

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?

The tool takes zero parameters and schema coverage is 100%, so the baseline of 4 applies. The description correctly adds no parameter detail because there are none to explain.

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 action and resource ('读取独立AI剧本创作入口的实时风格库' – read the real-time style library for the AI script creation entry), which is clear enough for an agent to know it returns available styles. It also implicitly distinguishes itself from pavo_apply_template and pavo_list_models by warning that canvas templates and model codes are not style IDs, though it never names those siblings directly.

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?

The second clause gives a negative guideline ('不把画布模板或模型code当风格ID'), telling the agent what not to supply, which implies this tool is the correct source of style IDs. However, there is no explicit statement of when to call it versus alternatives, and no prerequisites or sequencing guidance (e.g., call before pavo_script_create_ai).

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