mcp-1panel-plus

Overview Schema Source Related Servers Discussions Admin

Get Installed App Info

get_installed_app

Read-only

Retrieve status, version, and ports for a specific installed application by its ID on a selected 1Panel node; environment variables and compose files are excluded.

Instructions

Read status, version, and ports for a specific installed application ID on the selected node. Environment variables and compose files are excluded.

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

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.8/5.0

Behavior4/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. The description adds genuine context beyond that by bounding the payload: environment variables and compose files are explicitly excluded, and the read is scoped to the selected node. It stops short of noting permissions or visibility caveats for remote nodes.

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 tight sentences: the first front-loads what is returned and the targeting key, the second immediately delimits what is not returned. No filler, and the most decision-relevant constraint is placed early.

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 two-parameter read-only getter with no output schema, naming the returned fields (status, version, ports) and the exclusions gives the agent enough to know what it will get back and whether another tool is needed. Only minor gaps remain, such as behavior when the ID is invalid on the given node.

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 coverage is 100%, with both nodeId (including the 'local' convention and list_nodes reference) and app_install_id fully documented in the schema. The description only echoes the notion of an installed app ID and a selected node, adding no format or edge-case meaning. Baseline 3 applies when the schema carries the parameter semantics.

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 (read) and resource (status, version, ports for an installed application ID on a node), which is clearly narrower than the sibling list_installed_apps implied by 'a specific installed application ID'. The scope is unambiguous, though it never names the listing tool as the source of the ID.

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 'specific installed application ID' (i.e., use when you already have an ID, as opposed to enumerating), but there is no explicit when-to-use, no prerequisites, and no mention of alternatives for other kinds of app information. The agent must infer the workflow from the phrase alone.

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