Skip to main content
Glama
Sign In
Pavo 官网 MCP

Pavo 官网 MCP

by congliu1851-ui
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

读取项目历史产物

pavo_list_artifacts
Read-onlyIdempotent

List real historical artifacts for a project canvas by category (all, images, or videos) with date-grouped pagination to browse past generated media.

Instructions

读取项目历史真实产物。category=all/images/videos；该接口按日期分组分页，total不是文件总数。

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": {
      "project_uuid": "<project_uuid>",
      "canvas_uuid": "<canvas_uuid>"
    },
    "name": "pavo_list_artifacts"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
categoryNoall
page_sizeNo
canvas_uuidYes
project_uuidYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A3.7/5.0
Behavior4/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 covered. The description adds genuinely non-obvious behavior: results are paginated grouped by date, and the returned 'total' is not the file count — a detail that would otherwise mislead an agent computing page counts.

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 compact clauses, front-loaded with the purpose, then the allowed category values, then the pagination caveat. No filler and nothing repeated from structured fields.

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 return values need not be explained, and the total/pagination caveat is a valuable addition. However, for a five-parameter tool with zero schema coverage, the description leaves the meaning of the two required UUIDs and their relationship undefined.

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% across five parameters, so the description must compensate. It documents the category value set (all/images/videos), which the schema lacks, and clarifies pagination semantics for page/page_size, but says nothing about project_uuid or canvas_uuid or how the two scope the results.

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 verb and resource ('读取项目历史真实产物'), so an agent knows this tool reads historical artifacts for a project. It stops short of distinguishing itself from the existing sibling pavo_list_assets, leaving ambiguity about which list endpoint returns project history versus general assets.

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 only implied by 'historical artifacts of a project'; there is no explicit guidance on when to reach for this versus pavo_list_assets, pavo_list_nodes, or pavo_script_get_assets. No prerequisites or exclusions are stated.

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