Skip to main content
Glama
Sign In
Pavo 官网 MCP

Pavo 官网 MCP

by congliu1851-ui
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

设置角色四视图

pavo_script_set_character_four_view_image
Idempotent

Assigns an uploaded four-view character image to a state's image slot using verified state fingerprint and actual pixel dimensions. Reads back the target image without generating assets.

Instructions

将已上传的角色四视图设为指定状态的独立四视图图片位，原生字段为three_view_image。须提供get_assets对应states指纹及真实像素宽高；核归属、只读、同名状态及UNKNOWN，保存原生版本并回读目标图片和原有形象主图，保留描述、参考图、模型及绑定。不发起生成，不自动入素材库；官网无CAS，避免同时在网页编辑同一状态。

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_id": "<project_id>",
      "asset_id": "<asset_id>",
      "state_id": "<state_id>",
      "image_url": "<image_url>",
      "width": "<width>",
      "height": "<height>",
      "expected_sha256": "<expected_sha256>",
      "operation_id": "<operation_id>"
    },
    "name": "pavo_script_set_character_four_view_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
widthYes
heightYes
asset_idYes
state_idYes
image_urlYes
project_idYes
operation_idYes
thumbnail_urlNo
expected_sha256Yes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A4.1/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the pre-checks performed (ownership, read-only, same-name states, UNKNOWN), that it preserves description, reference images, model and bindings, and that it writes a native version then reads back both the target image and the pre-existing main image. It also flags the lack of CAS and the resulting concurrency hazard, which the openWorldHint annotation alone would not convey.

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?

Purpose and the native-field mapping are front-loaded in the first sentence, and Chinese semicolon packing keeps it compact for the amount of information conveyed. The middle segment stacks many clauses in a single run-on sentence, making it dense but not padded.

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?

Covers the risky parts well (pre-checks, preservation guarantees, concurrency), and the existing output schema means return values need no explanation. However, for a 9-parameter, 8-required mutation tool with zero schema descriptions, several parameters remain opaque, so the definition is not fully self-sufficient.

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 all parameter meaning; it only partially does. It clarifies width/height as the true pixel dimensions, ties the states fingerprint to pavo_script_get_assets (presumably expected_sha256), and implies image_url is a pre-uploaded image, but project_id, asset_id, operation_id, and thumbnail_url are left completely unexplained.

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: inserting an already-uploaded character four-view image into the dedicated four-view slot of a given state, and names the native field (three_view_image) it maps to. It explicitly excludes adjacent behaviors ('不发起生成，不自动入素材库'), which separates it from generation and asset-library tools in the sibling list.

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?

Gives a concrete prerequisite that routes the agent to a sibling tool: fetch the states fingerprint from pavo_script_get_assets, plus real pixel dimensions. It also warns against concurrently editing the same state in the web UI because the backend has no CAS. What it lacks is an explicit contrast with pavo_script_set_asset_main_image or pavo_script_save_asset_state, which also mutate asset imagery.

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