Skip to main content
Glama
Sign In
Pavo 官网 MCP

Pavo 官网 MCP

by congliu1851-ui
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

上传本地媒体

pavo_upload_media
Idempotent

Upload a specified local image, video, or audio file by absolute path and return a stable public URL and SHA; does not create nodes or save assets.

Instructions

上传明确指定的本地绝对路径图片、视频或音频，返回稳定public_url和SHA；不会自动创建节点或保存资产。

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

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.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=true, openWorldHint=true), so the bar is lower, yet the description still adds real value: it promises a stable public_url and SHA, which corroborates the idempotent hint, and explicitly bounds the side effects by saying no nodes are created and no assets are saved. Gaps remain on permissions, size limits, and supported formats.

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?

A single sentence with three clauses that each earn their place: what to upload, what comes back, and what is deliberately not done. The most important constraint is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 return-shape mention is a bonus rather than a requirement, and the description correctly focuses on scope boundaries. The missing piece is any hint about the required operation_id or about upload constraints (size, formats, auth), which matters for an open-world write operation.

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 must carry parameter meaning. It does explain 'path' well (local absolute path, restricted to image/video/audio content), but 'operation_id' is not mentioned at all, leaving one of two required parameters undocumented anywhere.

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?

States a specific verb (上传/upload) and a precise resource (本地绝对路径图片、视频或音频), and adds a negative scope clause (不会自动创建节点或保存资产) that separates it from pavo_create_node and pavo_save_node_asset. It stops just short of naming a sibling, so a 4 rather than a 5.

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 phrase '明确指定的本地绝对路径' implies the precondition for use (you must already know the exact local path), and the trailing clause hints that node/asset creation is a separate follow-up step. However, no sibling is named and there is no explicit 'use X instead when…' guidance, leaving the choice of pavo_save_node_asset or pavo_script_upload_file 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