Skip to main content
Glama

Build a basic matchmaker configuration

edgegap_build_matchmaker_config
Read-onlyIdempotent

Builds a ready-to-upload Edgegap matchmaker JSON config with team rules, latency limits, and wait-time expansions; verify the app version and save the file for manual dashboard upload.

Instructions

Generate a ready-to-upload Edgegap matchmaker JSON configuration with one profile: team count and size, optional latency rule, and optional expansions that relax the rules the longer a player waits. Checks the referenced application version exists and has ports. Edgegap has no API for creating a matchmaker, so this tool does NOT create one: save the returned config to a file (e.g. matchmaker-config.json) and have the developer upload it on the Matchmaker page of the dashboard. The matchmaker starts an authoritative dedicated server for each match, which is the recommended setup for multiplayer games.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "profile_name": "<profile_name>",
      "application": "<application>",
      "version": "<version>",
      "team_count": "<team_count>",
      "min_team_size": "<min_team_size>",
      "max_team_size": "<max_team_size>"
    },
    "name": "edgegap_build_matchmaker_config"
  }
}

Input Schema

NameRequiredDescriptionDefault
inspectNoExpose the inspection API for debugging. Default true; turn off for production.
versionYesVersion the matchmaker deploys.
expansionsNoRule relaxations after a player has waited this long, e.g. [{after_seconds: 20, min_team_size: 1}]. Keep each below ticket_expiration. Not needed for partial matches: min_team_size below max_team_size already allows them. Expansions cost the matchmaker performance, so add one only to relax a rule.
team_countYesTeams per match. 1 for free-for-all or co-op.
applicationYesApplication the matchmaker deploys.
profile_nameYesProfile clients will queue into, e.g. "casual-2v2".
max_team_sizeYes
min_team_sizeYes
max_latency_msNoAdds a latency rule: drop players above this ping to the chosen region. Needs beacon pings from the client.
verify_versionNoLook up the application version first. Default true.
ticket_expirationNoDefault "30s", so a developer testing alone is matched or told to retry within 30 s instead of waiting minutes. Raise it only for production queues.
allowed_cors_originsNoOrigins of web pages allowed to call the matchmaker, e.g. ["https://mygame.example.com", "http://localhost:8080"]. Required when game clients run in a browser (WebGL): browsers block matchmaker calls from any origin not listed. Scheme and host only, no path.
latency_difference_msNoMax ping spread between matched players. Default 100.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.13.3
    • changedInput schema / properties / expansions / description
      Previous value: -"Rule relaxations after a player has waited this long, e.g. [{after_seconds: 20, min_team_size: 1}]. Keep each below ticket_expiration."New value: +"Rule relaxations after a player has waited this long, e.g. [{after_seconds: 20, min_team_size: 1}]. Keep each below ticket_expiration. Not needed for partial matches: min_team_size below max_team_size already allows them. Expansions cost the matchmaker performance, so add one only to relax a rule."
  2. Changed2 schema fields changedv0.10.0
    • changedInput schema / properties / expansions / description
      Previous value: -"Rule relaxations after a player has waited this long, e.g. [{after_seconds: 30, min_team_size: 1}]."New value: +"Rule relaxations after a player has waited this long, e.g. [{after_seconds: 20, min_team_size: 1}]. Keep each below ticket_expiration."
    • changedInput schema / properties / ticket_expiration / description
      Previous value: -"Default \"5m\"."New value: +"Default \"30s\", so a developer testing alone is matched or told to retry within 30 s instead of waiting minutes. Raise it only for production queues."
  3. Changed1 schema field changedv0.5.2
    • addedInput schema / properties / allowed_cors_origins
      Added value: +{
      +  "description": "Origins of web pages allowed to call the matchmaker, e.g. [\"https://mygame.example.com\", \"http://localhost:8080\"]. Required when game clients run in a browser (WebGL): browsers block matchmaker calls from any origin not listed. Scheme and host only, no path.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  4. Addedv0.2.0

TDQS

A4.3/5.0
Behavior4/5

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

Goes beyond the readOnly/idempotent annotations by disclosing that it validates the referenced application version and its ports, that no resource is created server-side, and that a manual dashboard upload is required. The runtime note that each match spins up an authoritative dedicated server is useful context, though the shape of the returned JSON is not described.

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?

Four sentences, front-loaded with what is generated, followed by the manual-upload caveat and a closing rationale. No filler, though the final sentence about dedicated servers is context rather than call-critical.

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 13-parameter generator with no output schema, the description covers the essential contract: what it produces, what it verifies, and that creation happens outside the tool. It could go one step further in describing the returned artifact's contents, but the schema fills in the parameter-level detail.

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

Parameters3/5

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

Schema description coverage is 85%, so the input schema already carries most parameter meaning (expansions, latency, ticket_expiration, CORS). The description only gestures at the parameter set at a high level (team count/size, optional latency rule, expansions) without adding format or constraint detail beyond the schema. Baseline 3 is appropriate.

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 artifact: "Generate a ready-to-upload Edgegap matchmaker JSON configuration with one profile." It immediately lists the scope (team count/size, latency rule, expansions), so an agent knows exactly what this produces and how it differs from the deploy/version siblings.

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?

Explicitly says what the tool does NOT do and why ("Edgegap has no API for creating a matchmaker, so this tool does NOT create one"), then gives the required next step: save the config and upload via the dashboard. It also tells when to add expansions and when they are unnecessary.

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