Skip to main content
Glama
Sign In
Edgegap MCP Server

Edgegap MCP Server

Official
by edgegap
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List Edgegap applications

edgegap_list_apps
Read-only

Lists applications in your Edgegap organization so you can reuse an existing app before creating or deploying a duplicate.

Instructions

List the applications in the Edgegap organization. Start here before creating or deploying anything, so you reuse an existing application instead of making a duplicate. An "application" groups versions of one game server.

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_apps"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
limitNoResults per page, 1-100. Default 50.

Output Schema

NameRequiredDescriptionDefault
totalNo
showingNo
next_stepNo
truncatedNo
applicationsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.12.0
    • changedInput schema / properties / limit / description
      Previous value: -"Results per page. Default 50."New value: +"Results per page, 1-100. Default 50."
    • changedInput schema / properties / limit / maximum
      Previous value: -100New value: +9007199254740991
    • changedInput schema / properties / limit / minimum
      Previous value: -1New value: +-9007199254740991
    • changedInput schema / properties / page / minimum
      Previous value: -1New value: +-9007199254740991
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "applications": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "active": {
+            "type": "boolean"
+          },
+          "last_updated": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "next_step": {
+      "type": "string"
+    },
+    "showing": {
+      "type": "number"
+    },
+    "total": {
+      "type": "number"
+    },
+    "truncated": {
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}
  2. First observedv0.1.2

TDQS

A3.9/5.0
Behavior3/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 the organizational scope (whole org, no filtering) which is useful, but says nothing about pagination behavior or result volume, which matters for a list tool.

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?

Three short sentences, front-loaded with the action, then workflow guidance, then a definition. Every sentence earns its place with no filler.

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?

Output schema exists so return values need no explanation, and the tool is a simple read. The only real gap is pagination/parameter behavior, which lowers it from a 5 for a tool that returns potentially large org-wide lists.

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

Parameters2/5

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

Schema coverage is only 50%: 'limit' is documented, but 'page' has no description anywhere. The description adds no parameter guidance at all—no mention of paging, default page size, or how to iterate results—so it fails to compensate for the gap.

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 (List) and resource (applications in the Edgegap organization), and additionally defines what an 'application' is versus the sibling version tools: 'groups versions of one game server'. An agent can distinguish this from edgegap_list_app_versions without opening either 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?

'Start here before creating or deploying anything, so you reuse an existing application instead of making a duplicate' gives a clear precondition and intent, effectively routing the agent away from edgegap_create_app. It stops short of naming the sibling explicitly or saying when not to call it.

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