Skip to main content
Glama
bacarrdy

VPSnet

by bacarrdy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List compatible managed applications

list_application_catalog
Read-onlyIdempotent

List catalog applications compatible with a VPSnet service order before choosing an install method. Check product, OS, architecture, runtime compatibility and required credentials.

Instructions

List catalog applications compatible with one owned VPSnet service. Use this before a generic SSH installation and before install_application. The response includes application details, container runtime, configuration fields, hard product/OS/architecture/runtime compatibility, and advisory CPU/RAM/disk sizing warnings. Resource guidance alone must not block installation. Two blocks state what an install needs before you attempt it: target.install_requirements.runtime_restart_consent says whether this server still needs explicit restart consent, and each entry's secret_delivery says whether that release generates a password revealed only once and lists those credential NAMES. Those credentials often do not appear in configuration, which lists only customer-editable fields. Requires applications:read.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orderNoYesTenant-owned service order number: 1-64 ASCII letters, digits or hyphens, e.g. VP12345 or VP12345-1

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.3.16

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantial context beyond them: the response payload contents, that resource sizing guidance is advisory and 'must not block installation', that target.install_requirements.runtime_restart_consent signals pending restart consent, that secret_delivery marks one-time-revealed credentials whose NAMES do not appear in configuration, and the required applications:read scope.

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?

Front-loaded with the action and the when-to-use routing, followed by response detail. It is dense and somewhat long with multiple clauses about secret_delivery, but each sentence conveys operational information rather than filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Complete for a read-only catalog tool: purpose, workflow placement, response contents, compatibility/preflight semantics, credential caveats, and auth scope are all covered despite no output schema. An agent has everything needed to call and interpret it correctly.

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% and the single orderNo parameter is fully documented in the schema, so the description carries little additional parameter burden. It only implies the service-scoping via 'one owned VPSnet service'; baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('List catalog applications compatible with one owned VPSnet service'), scoping to a single service and clarifying it is a compatibility catalog rather than a listing of installed apps. This distinguishes it from siblings like list_service_applications, list_application_recipes, and install_application.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly prescribes placement in the workflow: 'Use this before a generic SSH installation and before install_application.' It names the alternative actions it should precede, so the agent knows exactly when to select it over those siblings.

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