Edgegap MCP Server

Official

by edgegap

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

Get one application version

edgegap_get_app_version

Read-only

Reads an Edgegap app version’s full configuration—image, resources, ports, caching, restart policy, log storage, and env var names—so you can validate it before updating or deploying.

Instructions

Read one version in full: image, resources, ports, max_duration, whether image caching (force_cache) and verify_image are on, restart policy, the Endpoint Storage its logs go to, and the names of its env vars (values are never shown). Use it before edgegap_update_app_version or edgegap_deploy to check what a version will do.

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>",
      "version": "<version>"
    },
    "name": "edgegap_get_app_version"
  }
}

Input Schema

Name	Required	Description	Default
`version`	Yes	Version name, as listed by edgegap_list_app_versions.
`application`	Yes	Application name.

Output Schema

Name	Required	Description	Default
`env`	No
`name`	No
`image`	No
`ports`	No
`active`	No
`warning`	No
`auto_stop`	No
`cpu_units`	No
`memory_mb`	No
`application`	No
`force_cache`	No
`verify_image`	No
`restart_policy`	No
`caching_percent`	No
`endpoint_storage`	No
`max_duration_minutes`	No
`auto_stop_after_minutes`	No
`registry_credentials_set`	No
`termination_grace_period_seconds`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.15.1Oct 29, 2026
- addedOutput schema / properties / endpoint_storage
```
Added value: +{
+  "type": "string"
+}
```

Changed1 schema field changedv0.12.0Oct 27, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "active": {
+      "type": "boolean"
+    },
+    "application": {
+      "type": "string"
+    },
+    "auto_stop": {
+      "type": "string"
+    },
+    "auto_stop_after_minutes": {
+      "type": "number"
+    },
+    "caching_percent": {
+      "type": "number"
+    },
+    "cpu_units": {
+      "type": "number"
+    },
+    "env": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "hidden": {
+            "type": "boolean"
+          },
+          "key": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "force_cache": {
+      "type": "boolean"
+    },
+    "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"
+    },
+    "restart_policy": {
+      "type": "string"
+    },
+    "termination_grace_period_seconds": {
+      "type": "number"
+    },
+    "verify_image": {
+      "type": "boolean"
+    },
+    "warning": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Addedv0.7.1Oct 22, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover read-only and open-world hints, so the description's added value is the disclosure that env var values are never returned — a meaningful safety/redaction detail an agent needs. It also scopes the read ('one version in full'), though it says nothing about rate limits or error behavior.

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 sentences, zero filler. The payload contents come first and the usage cue comes second, so the most selection-relevant information is front-loaded.

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 the field enumeration is partly redundant, but it usefully doubles as a selection aid. Safety is covered by annotations and the env-var redaction note. Nothing critical is missing, though it could note that this is the only way to inspect a single version's config.

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%, with both 'application' and 'version' documented, including a pointer to edgegap_list_app_versions for valid version names. The description adds no parameter-level detail beyond the schema, 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?

Opens with a specific verb and resource ('Read one version in full') and then enumerates exactly what is returned: image, resources, ports, max_duration, cache flags, restart policy, Endpoint Storage, env var names. That enumeration distinguishes it cleanly from edgegap_list_app_versions and edgegap_create_app_version without needing the schema.

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?

Explicitly states when to reach for it: 'Use it before edgegap_update_app_version or edgegap_deploy to check what a version will do.' That names the downstream siblings and the decision point. It stops short of stating exclusions (e.g., 'use list_app_versions to browse'), so it is a strong 4 rather than a 5.

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

Deploy Server