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 relay sessions

edgegap_list_relay_sessions
Read-only

List this organization's active relay sessions: id, status, readiness and player count. Relay sessions bill while open, so use this to find ones left over from earlier sessions and delete them with edgegap_delete_relay_session. Authorization tokens are not listed; read one session with edgegap_get_relay_session.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
totalNo
showingNo
sessionsNo
next_stepNo
truncatedNo

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": {
+    "next_step": {
+      "type": "string"
+    },
+    "sessions": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "error": {
+            "type": "string"
+          },
+          "linked": {
+            "type": "boolean"
+          },
+          "players": {
+            "type": "number"
+          },
+          "ready": {
+            "type": "boolean"
+          },
+          "relay": {
+            "type": "string"
+          },
+          "session_id": {
+            "type": "string"
+          },
+          "status": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "showing": {
+      "type": "number"
+    },
+    "total": {
+      "type": "number"
+    },
+    "truncated": {
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}
  2. Added

TDQS

A4.7/5.0
Behavior4/5

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

Beyond readOnlyHint/openWorldHint, it discloses two non-obvious traits: sessions bill while open (cost risk) and authorization tokens are deliberately excluded from the listing. Doesn't mention result shape/pagination, but with 0 params and an output schema that gap is minor.

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: what it returns, why it matters (billing), and where to go instead. Front-loaded with no filler.

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?

Complete for a no-arg list tool: annotations cover the safety profile, an output schema covers return values, and the description still adds the billing and token-exclusion context an agent needs to act on the result.

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?

Zero parameters, so there is nothing for the description to disambiguate; baseline is 4. The description correctly implies an unscoped org-wide listing rather than inviting and mis-documenting filters.

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 ('List this organization's active relay sessions') plus the exact fields returned (id, status, readiness, player count). Clearly distinguishable from edgegap_get_relay_session, which it names as the single-session reader.

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?

Explicit when-to-use: find leftover sessions from earlier runs and clean them up with edgegap_delete_relay_session; use edgegap_get_relay_session to read one. Both the alternative and the follow-up action are named.

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