Skip to main content
Glama
Sign In
Pavo 官网 MCP

Pavo 官网 MCP

by congliu1851-ui
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

读取参考连接

pavo_list_connections
Read-onlyIdempotent

Reads the authoritative connection list for a Pavo project canvas, preserving role, port, and media_order so dependencies are not guessed from node data.source.

Instructions

读取权威connection_list，保留role、端口、media_order；不以节点data.source猜依赖。

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

Input Schema

NameRequiredDescriptionDefault
canvas_uuidYes
project_uuidYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

B3.4/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 safety is covered. The description adds genuine context beyond that: the returned list is the authoritative source and is passed through with role/port/media_order intact, plus a caution against deriving dependencies from node data.source.

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?

A single compact sentence that front-loads the resource and the authoritative-list guarantee, then adds the caveat. Nothing is padded, and the terseness that remains is largely justified rather than accidental.

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?

The presence of an output schema means the description need not explain the return shape, and the annotations carry the safety profile. The remaining gap is that neither required parameter is characterized anywhere, leaving the agent without guidance on what project_uuid/canvas_uuid must identify.

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% for two required parameters (project_uuid, canvas_uuid), and the description does not mention either. It says nothing about scoping or the expected UUID format, so the description does not compensate for the coverage gap.

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 and resource: read the authoritative connection_list, and names the fields it preserves (role, port, media_order). That distinguishes it in substance from pavo_connect_references (which creates links) and from inspecting pavo_list_nodes, though neither sibling is named explicitly.

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 clause 'do not guess dependencies from node data.source' implicitly tells the agent to prefer this tool over inferring links from node payloads, which is real usage guidance. However, it never names the alternative tools (e.g. pavo_list_nodes) or states preconditions such as when a canvas has no connections yet.

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