mcp-1panel-plus

Overview Schema Source Related Servers Discussions Admin

Get Available App Upgrade Versions

get_app_update_versions

Read-only

Lists available upgrade versions (detailId and version) for an installed app ID on a selected node, so you can choose a target version before updating.

Instructions

List target upgrade versions (detailId and version) available for a specific installed app ID on the selected node.

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": {
      "app_install_id": "<app_install_id>"
    },
    "name": "get_app_update_versions"
  }
}

Input Schema

Name	Required	Description	Default
`nodeId`	No	Target node ID: "local" for the Main Node, or a numeric string ID (e.g. "3") from list_nodes.	local
`app_install_id`	Yes	Numeric installed app ID.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 11, 2026

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 the safety profile is covered by structured data. The description adds that results are scoped per node and enumerates the two returned fields, but says nothing about ordering, completeness of the version list, or error behavior when the app ID is not installed.

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 front-loaded sentence with no filler, and the returned field names are placed inline where they are most useful. It is efficient, though it is terse enough that it reads more like a label than guidance.

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 no output schema, the description usefully names the two returned fields (`detailId`, `version`), and the read-only nature is covered by annotations while the required parameter is fully documented in the schema. What remains thin is the upgrade workflow context — what to do with the returned `detailId` next — but nothing essential for invoking the tool is missing.

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%, so both `nodeId` (with its "local" vs numeric-string rule) and `app_install_id` are already documented. The description reinforces that the ID must be an installed app and that `nodeId` selects the node, but adds no new syntax, ranges, or defaults beyond the schema.

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 ("List target upgrade versions") plus the exact fields returned (`detailId` and `version`), scoped to an installed app on a node. It does not name or contrast with the sibling `list_app_versions`, so an agent must infer the distinction between listing available store versions and listing upgrade targets for an installed app.

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: the definition says the versions are "for a specific installed app ID on the selected node," which hints the app must already be installed and that this feeds an upgrade operation. There is no explicit when-to-use, when-not-to-use, or pointer to alternatives such as `list_app_versions` or `operate_installed_app`.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.