Skip to main content
Glama

List versions of an application

edgegap_list_app_versions
Read-only

List an application's versions with container image, resources, ports, TLS upgrade status, and registry login status to choose a version to deploy, verify readiness, or copy non-secret settings.

Instructions

List the versions under an application, with their container image, resources, ports (including whether TLS Upgrade is on, which browser/WebGL clients need for wss://) and whether a registry login is set for pulling the image. Use this to find the version name to deploy, to check a version is ready before deploying, or to copy the non-secret settings (image, resources, ports) of a working version when creating a new one. The registry login and secret env values are never readable: the API returns "This value is set and encrypted" for them, so get them from the dashboard's Container Registry page or the developer.

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

Input Schema

NameRequiredDescriptionDefault
applicationNoApplication name, as returned by edgegap_list_apps. Required; without it the applications are listed.

Output Schema

NameRequiredDescriptionDefault
totalNo
showingNo
versionsNo
next_stepNo
truncatedNo
applicationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.19.5
    • changedInput schema / properties / application / description
      Previous value: -"Application name, as returned by edgegap_list_apps."New value: +"Application name, as returned by edgegap_list_apps. Required; without it the applications are listed."
    • removedInput schema / required
      Removed value: -[
      -  "application"
      -]
  2. Changed1 schema field changedv0.12.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": {},
      +  "properties": {
      +    "application": {
      +      "type": "string"
      +    },
      +    "next_step": {
      +      "type": "string"
      +    },
      +    "showing": {
      +      "type": "number"
      +    },
      +    "total": {
      +      "type": "number"
      +    },
      +    "truncated": {
      +      "type": "boolean"
      +    },
      +    "versions": {
      +      "items": {
      +        "additionalProperties": {},
      +        "properties": {
      +          "active": {
      +            "type": "boolean"
      +          },
      +          "cpu_units": {
      +            "type": "number"
      +          },
      +          "image": {
      +            "type": "string"
      +          },
      +          "max_duration_minutes": {
      +            "type": "number"
      +          },
      +          "memory_mb": {
      +            "type": "number"
      +          },
      +          "name": {
      +            "type": "string"
      +          },
      +          "ports": {
      +            "items": {
      +              "additionalProperties": {},
      +              "properties": {
      +                "name": {
      +                  "type": "string"
      +                },
      +                "port": {
      +                  "type": "number"
      +                },
      +                "protocol": {
      +                  "type": "string"
      +                },
      +                "tls_upgrade": {
      +                  "type": "boolean"
      +                }
      +              },
      +              "type": "object"
      +            },
      +            "type": "array"
      +          },
      +          "registry_credentials_set": {
      +            "type": "boolean"
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "type": "object"
      +}
  3. First observedv0.1.2

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description goes well beyond them by disclosing a real behavioral constraint: registry logins and secret env values are never returned in plaintext and come back as "This value is set and encrypted", with a pointer to the dashboard or developer as the workaround. That is exactly the kind of redaction/auth caveat an agent needs before concluding data is missing.

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 its output fields, then the use cases, then the secrets caveat. Every clause carries information, though the parenthetical about browser/WebGL wss:// clients is slightly tangential to an agent's decision to call the tool.

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?

An output schema exists, so return-shape detail is unnecessary, and the description covers purpose, use cases, and the encryption caveat. The only meaningful omission is pagination or result-count behavior for an application with many versions, which would matter for a listing tool.

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?

The single `application` parameter is fully documented in the schema, including the important fallback that omitting it lists applications instead of versions. The description text itself adds nothing about the parameter, so with 100% schema coverage the baseline of 3 applies.

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?

Opens with a specific verb and resource ("List the versions under an application") and immediately enumerates what each entry contains: container image, resources, ports, TLS Upgrade status, and registry-login presence. That is far more than a restatement of the name. It stops short of 5 because it never explicitly contrasts itself with the singular edgegap_get_app_version or edgegap_compare_versions, leaving the agent to infer the list-vs-single distinction.

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

Usage Guidelines4/5

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

Gives three concrete situations to reach for this tool: finding the version name to deploy, verifying a version is ready before deploying, and copying non-secret settings when creating a new version. That is clear, task-oriented guidance rather than implied usage. It does not name an alternative tool or state when to prefer get_app_version instead, so it falls short of the 5 bar.

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