Skip to main content
Glama
Sign In
mcp-1panel-plus

mcp-1panel-plus

by EC061
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Check 1Panel Main & Child Upgrades

check_panel_upgrades
Read-only

Inspect 1Panel versions across the main node and X-Pack child nodes, compare them with upstream releases, and report which nodes need upgrades.

Instructions

Inspect current 1Panel versions on the Main Node and all X-Pack Child Nodes, check available upstream 1Panel releases, and report which nodes have pending upgrades.

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": "check_panel_upgrades"
  }
}

Input Schema

NameRequiredDescriptionDefault
max_releasesNoNumber of recent upstream releases to list.
include_release_notesNoInclude markdown release notes for the latest available version.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety and network access are covered. The description usefully adds that it queries upstream releases and covers all child nodes, but it says nothing about latency, auth requirements, or failure behavior when a node is unreachable.

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, well-formed sentence with the scope front-loaded and no filler. It could be marginally improved by splitting the check-versus-report actions, but nothing is wasted.

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?

For a simple read-only inspection tool with no output schema, the description adequately conveys what is examined and roughly what is reported (pending upgrades per node). It is not exhaustive about the response shape, but the annotations and schema cover the rest.

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 100%, and both parameters (max_releases, include_release_notes) have their own descriptions and bounds, so the schema carries the burden. The description adds no extra meaning about these options, which is acceptable at this coverage level.

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 specific verbs and resources: it inspects 1Panel versions on the Main Node and X-Pack Child Nodes, checks upstream releases, and reports pending upgrades. That clearly separates it from siblings like get_child_node_upgrade_logs or get_app_update_versions, although it does not name those alternatives 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?

Usage is implied by the described scope — an agent can infer this is the pre-upgrade status check across nodes — but there is no explicit when-to-use versus when-not, no mention of prerequisites, and no pointer to the logs tool for follow-up diagnosis.

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