Skip to main content
Glama
Sign In

Edgegap

by dev.edgegap
OverviewDiscussionsAdmin
This connector has been deprecated

older mcp we are replacing it with another one.

List versions of an application

edgegap_list_app_versions
Read-only

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

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": {
      "application": "<application>"
    },
    "name": "edgegap_list_app_versions"
  }
}

Input Schema

NameRequiredDescriptionDefault
applicationYesApplication name, as returned by edgegap_list_apps.

Output Schema

NameRequiredDescriptionDefault
totalNo
showingNo
versionsNo
next_stepNo
truncatedNo
applicationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/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"
+}
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only say readOnly/openWorld; the description adds a non-obvious constraint — registry logins and secret env values are never readable and come back as "This value is set and encrypted" — plus where to get them instead. That prevents an agent from retrying or misinterpreting the response, which is exactly the value-add expected beyond annotations.

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 what is returned, then purposes, then the secrets caveat. Dense but each sentence carries information; the WebGL parenthetical is mildly verbose but justifies why TLS Upgrade matters for wss:// clients.

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?

Output schema documents the shape, annotations cover safety, and the description covers the one thing structured data cannot: that certain fields are intentionally redacted and where to obtain them. Nothing needed to call this correctly 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 coverage is 100% and the schema already explains that 'application' is the name returned by edgegap_list_apps. The description adds no further semantics about the parameter (format, case sensitivity, error on unknown name), so the baseline 3 applies.

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+resource (list versions under an application) and enumerates the salient returned fields: container image, resources, ports with TLS Upgrade status, and registry-login presence. This distinguishes it cleanly from edgegap_list_apps and edgegap_get_app_version.

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?

Three concrete use cases are given: find a version name to deploy, verify readiness before deploying, and copy non-secret settings when creating a new version. It also points to the dashboard's Container Registry page for the values this API cannot return. No explicit exclusion of edgegap_get_app_version for single-version lookups, so it stops short of a 5.

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

All Edgegap toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources