Skip to main content
Glama
Sign In
Pavo 官网 MCP

Pavo 官网 MCP

by congliu1851-ui
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

读取项目列表

pavo_list_projects
Read-onlyIdempotent

Retrieve the project list for the currently logged-in Pavo website account, so you can review and select projects to manage.

Instructions

读取当前官网登录账号的项目列表。

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description's one added piece of context is the scoping to the current official-site login account, which implies an auth prerequisite and a bounded result set. It says nothing about ordering, pagination, or what happens when unauthenticated, so it adds only modest value beyond the annotations.

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 short sentence with zero filler and the scope qualifier (当前官网登录账号) placed before the resource. It is efficient, though it borders on under-specification rather than achieving maximum information density.

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 and rich annotations, the description need not explain return values, and it covers the essential scope. However, given 60+ sibling tools and two other project-listing/project-getting tools in the same namespace, it is not complete enough to let an agent choose confidently without extra inference.

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

Parameters4/5

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

The tool takes zero parameters, so there is no parameter semantics to document and the baseline of 4 applies. The description correctly implies the only implicit input is the logged-in account context rather than an explicit argument.

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 states a specific verb (读取/read) and resource (项目列表/project list) and scopes it to the currently logged-in official-site account, so an agent knows exactly what is returned. It does not differentiate this from near-siblings such as pavo_script_list_projects or pavo_get_project, which is the only thing keeping it from 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to call this versus pavo_script_list_projects, pavo_get_project, or pavo_create_project, and no prerequisites or exclusions are stated. The agent must infer usage purely from the tool name.

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