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 where servers can run

edgegap_list_locations
Read-only

List the cities Edgegap can deploy to. Pass application and version to see only the locations with capacity for that version right now. Use it to pick geo_coordinates for edgegap_deploy when you have no player IPs, or to tell a developer where their players can be served from. For the ping beacons game clients use to measure latency, see edgegap_list_ping_beacons.

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

Input Schema

NameRequiredDescriptionDefault
pageNo
limitNoDefault 100.
versionNo
applicationNoWith version: only locations with capacity for it now.

Output Schema

NameRequiredDescriptionDefault
totalNo
showingNo
messagesNo
locationsNo
next_stepNo
truncatedNo
filtered_forNo

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": {
+    "filtered_for": {
+      "type": "string"
+    },
+    "locations": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "city": {
+            "type": "string"
+          },
+          "continent": {
+            "type": "string"
+          },
+          "country": {
+            "type": "string"
+          },
+          "latitude": {
+            "type": "number"
+          },
+          "longitude": {
+            "type": "number"
+          },
+          "region": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "messages": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "next_step": {
+      "type": "string"
+    },
+    "showing": {
+      "type": "number"
+    },
+    "total": {
+      "type": "number"
+    },
+    "truncated": {
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}
  2. Added

TDQS

A4.5/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 the safety profile is covered. The description adds genuinely useful context: passing application+version filters to locations with capacity *right now*, an important point-in-time behavior. However it says nothing about result set size, ordering, or rate limits, so it adds value but not rich behavioral context.

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 tight sentences, front-loaded with the core action, then conditional filtering, then use cases and the sibling hand-off. Every sentence carries new information.

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?

Annotations carry the safety profile and an output schema exists to describe return values, so the description doesn't need to. It covers purpose, filter behavior, use cases, and the nearest sibling, leaving no material gap for an agent to call it correctly.

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 50%; the description compensates for the undocumented application/version pairing by explaining the combined filter semantics ('Pass application and version to see only the locations with capacity for that version right now'). page and limit remain uncovered, though 'Default 100' is already in the schema for limit.

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 and resource: 'List the cities Edgegap can deploy to.' It explicitly differentiates from the sibling edgegap_list_ping_beacons by naming it and describing that tool's distinct purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives two concrete use cases (picking geo_coordinates for edgegap_deploy when no player IPs exist, or reporting serving locations to a developer) and routes the latency-beacon use case to the named alternative. Nothing is left to inference.

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