Skip to main content
Glama
edgegap

Edgegap MCP Server

Official
by edgegap
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List running deployments

edgegap_list_deployments
Read-only

List active deployments, optionally filtered and sorted. Use this to find deployments left running from earlier sessions before starting new ones — orphaned servers cost money.

Instructions

List active deployments, optionally filtered and sorted. Use this to find deployments left running from earlier sessions before starting new ones — orphaned servers cost money. Filter by status, application, version, tags, request_id, created_at, fleet_name or host_name, e.g. [{field:"application",operator:"eq",value:"my-game"},{field:"status",operator:"eq",value:"ready"}]. Operators: eq and neq on every field except created_at (eq, gte, lte); in and nin with an array value on request_id, tags, application, version, fleet_name, host_name; ilike with % wildcards on fleet_name and host_name. At most one filter per field. Sort by created_at or available_session_sockets. To find every deployment an agent started through this server, pass only_agent_deployments: true (the same as filtering tags in ["edgegap-mcp", "mcp"]).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoDefault 50.
filtersNoOmit for all deployments.
order_byNoe.g. [{field:"created_at",order:"asc"}] for oldest first.
only_agent_deploymentsNoOnly deployments started through this server: tagged "edgegap-mcp", or "mcp" by versions up to 0.3.3. Cannot be combined with a tags filter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.2
    • addedInput schema / properties / only_agent_deployments
      Added value: +{
+  "description": "Only deployments started through this server: tagged \"edgegap-mcp\", or \"mcp\" by versions up to 0.3.3. Cannot be combined with a tags filter.",
+  "type": "boolean"
+}
  2. Changed3 schema fields changedv0.2.2
    • removedInput schema / properties / filter
      Removed value: -{
-  "description": "Edgegap filter expression, e.g. by tag. Omit for all deployments.",
-  "type": "string"
-}
    • addedInput schema / properties / filters
      Added value: +{
+  "description": "Omit for all deployments.",
+  "items": {
+    "properties": {
+      "field": {
+        "enum": [
+          "status",
+          "request_id",
+          "tags",
+          "created_at",
+          "application",
+          "version",
+          "fleet_name",
+          "host_name"
+        ],
+        "type": "string"
+      },
+      "operator": {
+        "enum": [
+          "eq",
+          "neq",
+          "in",
+          "nin",
+          "gte",
+          "lte",
+          "ilike"
+        ],
+        "type": "string"
+      },
+      "value": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          }
+        ],
+        "description": "A string, or an array of strings for in/nin. created_at is ISO 8601, e.g. \"2026-09-30T00:00:00Z\"."
+      }
+    },
+    "required": [
+      "field",
+      "operator",
+      "value"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / order_by
      Added value: +{
+  "description": "e.g. [{field:\"created_at\",order:\"asc\"}] for oldest first.",
+  "items": {
+    "properties": {
+      "field": {
+        "enum": [
+          "created_at",
+          "available_session_sockets"
+        ],
+        "type": "string"
+      },
+      "order": {
+        "enum": [
+          "asc",
+          "desc"
+        ],
+        "type": "string"
+      }
+    },
+    "required": [
+      "field",
+      "order"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
  3. 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 already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds real behavioral constraints beyond that: at most one filter per field, operator availability varies by field, and only_agent_deployments cannot be combined with a tags filter. It does not describe the return shape or result volume, which is a minor gap for a tool with no output schema.

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?

Purpose and the motivating use case are front-loaded, followed by the filter grammar. It is long, but the length is driven by genuinely dense query semantics rather than filler, and it includes worked examples. Slightly heavy for a single description but each clause carries 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 read-only, annotated list tool whose schema already defines limit and filter structure, the description supplies enough to call it correctly, including caveats and examples. The remaining gap is that it never characterizes the returned deployment objects, which matters somewhat given there is no output schema.

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

Parameters5/5

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

Schema coverage is 100%, setting the baseline at 3, but the description meaningfully exceeds it: it maps which operators are valid per field (eq/neq everywhere except created_at, which uses eq/gte/lte; in/nin on specific fields; ilike with % wildcards only on fleet_name and host_name) and documents the only_agent_deployments equivalence to a tags filter. That per-field operator grammar is not inferable from the schema's flat operator enum.

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+resource+scope ("List active deployments, optionally filtered and sorted"), which cleanly distinguishes it from the singular edgegap_get_deployment and from edgegap_deploy/edgegap_stop_deployment. An agent can identify the operation without opening 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?

Gives a concrete when-to-use scenario with a rationale: find deployments left running from earlier sessions before starting new ones because orphaned servers cost money. It also routes a special case (only_agent_deployments for agent-started servers). It stops short of naming explicit alternatives for single-deployment lookups (get_deployment) or exclusions.

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