Skip to main content
Glama
edgegap

Edgegap MCP Server

Official
by edgegap
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Create an application version

edgegap_create_app_version

Register a container image as a deployable application version. Specify CPU, memory, ports, and registry credentials; verify the image to catch deployment issues early.

Instructions

Register a container image as a deployable version of an application. The image must already be pushed to a registry that Edgegap can pull from (see edgegap_get_registry_credentials and edgegap_list_registry_tags). Resource units: 1024 cpu units = 1 vCPU; memory_mb must be at least 256 and at most double the cpu units. Set verify_image true on the first version so a bad image fails here rather than at deploy time. Avoid the "latest" docker tag — use a build ID so deployments are reproducible.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
envNoEnvironment variables injected into the container.
nameYesVersion identifier, typically a build ID or timestamp.
portsYesPorts to expose. At least one is required for players to connect.
cpu_unitsYesvCPU units. 1024 = 1 vCPU.
memory_mbYesMemory in MB. At most 2x cpu_units.
docker_tagYesImage tag. Use a build ID, not "latest".
applicationYesExisting application name.
docker_imageYesNamespaced image, e.g. "mystudio/game-server".
verify_imageNoVerify Edgegap can pull the image before accepting the version.
registry_tokenNoRegistry password or token.
docker_repositoryYesRegistry host, e.g. "docker.io" or "registry.edgegap.com".
registry_usernameNoRegistry username, for private images.
max_duration_minutesNoAuto-stop after this many minutes. Keeps test deployments from running up cost.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.0
    • changedInput schema / properties / ports / items / properties / protocol / description
      Previous value: -"UDP, TCP, WS, or HTTP. Most game servers use UDP."New value: +"One of UDP, TCP, TCP/UDP, HTTP, HTTPS, WS, WSS. Most game servers use UDP."
  2. First observedv0.1.2

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only supply openWorldHint/idempotentHint/destructiveHint; the description adds real behavioral context beyond them: the external-registry dependency, that verify_image makes a bad image fail here rather than at deploy time, and that reproducible tags prevent flaky deploys. It does not state permissions/error behavior, keeping it short of a 5.

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?

Five sentences, purpose front-loaded, then prerequisites, then resource-unit rules, then two actionable tips. No filler and every clause carries operational information.

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 13-parameter mutation with no output schema and only safety-oriented annotations, the description covers the key unknowns: registry prerequisites, resource-unit math, verification, and tag hygiene. It omits version-name uniqueness expectations and any indication of the response payload, but the core call path is complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds cross-parameter meaning absent from any single schema field: the 1024-units-per-vCPU conversion and the memory_mb >= 256 / <= 2x cpu_units constraint. Usage semantics for verify_image ('first version') also go beyond the schema text.

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?

Specific verb+resource ('Register a container image as a deployable version of an application') that clearly separates it from sibling edgegap_create_app and edgegap_list_app_versions. An agent can tell exactly what object is being created and from what input.

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 concrete preconditions (image must already be pushed to a registry Edgegap can pull from) and routes the agent to edgegap_get_registry_credentials and edgegap_list_registry_tags for verification. It advises setting verify_image on the first version and avoiding the 'latest' tag, but doesn't explicitly contrast with edgegap_create_app for the 'when not to use' case.

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