Skip to main content
Glama

List ping beacons

edgegap_list_ping_beacons
Read-only

List Edgegap ping beacons by region so game clients can measure latency before matchmaking. Read-only retrieval of one host per region for UDP or TCP pings.

Instructions

List Edgegap's ping beacons: one host per region that a game client can ping (UDP or TCP) to measure its latency before matchmaking. The matchmaker's latency rules use these measurements. Read-only; the game client does the pinging, not this tool.

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

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
totalNo
beaconsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.19.5
    • changedInput schema / properties / limit / description
      Previous value: -"Default 100."New value: +"Results per page, 1-200. Default 100."
    • changedInput schema / properties / limit / maximum
      Previous value: -200New value: +9007199254740991
    • changedInput schema / properties / limit / minimum
      Previous value: -1New value: +-9007199254740991
  2. Changed1 schema field changedv0.12.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": {},
      +  "properties": {
      +    "beacons": {
      +      "items": {
      +        "additionalProperties": {},
      +        "properties": {
      +          "city": {
      +            "type": "string"
      +          },
      +          "continent": {
      +            "type": "string"
      +          },
      +          "country": {
      +            "type": "string"
      +          },
      +          "host": {
      +            "type": "string"
      +          },
      +          "tcp_port": {
      +            "type": "number"
      +          },
      +          "udp_port": {
      +            "type": "number"
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "total": {
      +      "type": "number"
      +    }
      +  },
      +  "type": "object"
      +}
  3. Addedv0.7.1

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the bar is lower; the description still adds real value by clarifying that the game client does the pinging rather than the tool, preventing a false expectation of side effects or network probes. It says nothing about pagination or result volume, which would have made it complete, but the output schema covers the return shape.

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?

Two tight sentences, front-loaded with the verb and resource, with the clarifying definition followed immediately by the read-only scope note. No filler or repetition of schema content.

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 simple read-only list with an output schema and annotations, the description supplies the essential domain meaning (what a beacon is, who pings it, how matchmaking consumes it). The only notable gap is pagination guidance, which the output schema partially offsets.

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 50% – only `limit` is described – and the description adds nothing about `page` or paging behavior, so it does not compensate for the undocumented parameter. An agent must infer pagination semantics entirely from the bare schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource ('List Edgegap's ping beacons') and defines the concept concretely: one host per region, pingable over UDP or TCP to measure latency before matchmaking. It does not explicitly name a sibling such as edgegap_list_locations to disambiguate from, so it falls short of the top score, but an agent can still tell what it returns.

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

Usage Guidelines3/5

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

Usage is only implied: the mention that 'the matchmaker's latency rules use these measurements' hints at the purpose of the data, but there is no explicit when-to-call guidance, no prerequisites, and no named alternative for latency/region lookups. The last clause usefully excludes one misreading (that this tool performs pinging).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.