Skip to main content
Glama
Sign In
Pavo 官网 MCP

Pavo 官网 MCP

by congliu1851-ui
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

读取AI剧本项目

pavo_script_list_projects
Read-onlyIdempotent

Retrieves a paginated list of Pavo script projects for browsing or managing episodes; set is_demo to true to read the official read-only demo without making changes.

Instructions

分页查询官网/playlet/list剧本项目。is_demo=true读取官方只读演示，不可修改。

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_projects"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
is_demoNo
page_sizeNo

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 non-destructive behavior, so the safety profile is covered; the description adds that demo data is official and cannot be modified, which is genuinely extra context. It does not mention pagination limits, ordering, or what distinguishes demo projects from normal ones, which is the behavior an agent most needs here.

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

Conciseness5/5

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

Two short sentences with no filler, and the core action is front-loaded ahead of the is_demo caveat. Nothing could be removed without losing information.

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, return values need not be described, and the read-only annotations cover safety, so this is close to sufficient for a three-parameter list tool. The gaps are the lack of differentiation from the sibling list/get project tools and the absence of any parameter detail for page/page_size.

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

Parameters3/5

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

Schema description coverage is 0%, so the description bears the burden; it explains is_demo's semantics (official read-only demo) but leaves page and page_size to the schema titles and defaults. The phrase 分页查询 does imply the purpose of the pagination pair, which is partial compensation, but no bounds, max page size, or default behavior is stated.

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 gives a specific verb and resource (分页查询剧本项目, paginated listing of script projects) and names the backing endpoint /playlet/list, so the agent knows it is a list operation over script projects. It does not, however, distinguish itself from the sibling pavo_list_projects or pavo_script_get_project, so the agent must infer which project-listing tool applies.

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?

It provides one concrete usage cue: pass is_demo=true to read the official read-only demo set. There is no guidance on when to choose this over pavo_list_projects or pavo_script_get_project, and no note on when the demo vs. non-demo path should be used beyond the read-only remark.

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