Skip to main content
Glama
Sign In
Pavo 官网 MCP

Pavo 官网 MCP

by congliu1851-ui
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

连接和登录状态

pavo_server_status
Read-onlyIdempotent

Reads masked Pavo account login status without contacting the official site or returning credentials, and reports JWT expiry as a local-only hint for session checks.

Instructions

读取脱敏登录状态，不访问官网、不返回凭证。JWT到期值仅用于本地提示，未做签名认证。

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), yet the description adds genuinely new behavior: it does not contact the official site, never returns credentials, and the JWT expiry value is unverified and only a local hint. The unverified-JWT caveat is the kind of disclosure an agent needs so it does not treat a reported expiry as authoritative.

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 short clauses with zero filler, leading with what is read and immediately bounding what is deliberately withheld (no network access, no credentials). Every phrase carries information an agent would otherwise have to guess.

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?

With an output schema present, return values need not be explained, and the description covers the remaining non-obvious aspects: data is sanitized, no remote verification occurs, and the JWT expiry is informational only. What is missing is guidance on what an agent should do when status reports logged-out, which would matter for a connectivity-gate tool.

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 nothing for the description to disambiguate and the baseline of 4 applies. The description correctly spends no words on parameter explanation.

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 gives a specific verb+resource (读取脱敏登录状态, 'read sanitized login status') that is distinct from every sibling tool in the list, which are project/node/script/asset operations. It does not explicitly name a sibling or contrast case, so differentiation is by obvious domain separation rather than stated routing.

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: an agent can infer this is the pre-flight/health-check call before auth-dependent operations. There is no explicit 'use this when...' statement, no mention of prerequisites for login, and no alternative tool named for the case where status is unhealthy or credentials are missing.

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