Skip to main content
Glama

Get available locations

gameye_get_locations
Read-onlyIdempotent

Retrieve available regions and datacenters for a Docker game image, including ping IPs for latency testing; without an API token, returns setup steps instead.

Instructions

Get the list of available regions/datacenters that can host a given game image, along with ping IPs for latency testing. Needs GAMEYE_API_TOKEN; without one, returns setup steps and sends nothing.

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": {
      "image": "<image>"
    },
    "name": "gameye_get_locations"
  }
}

Input Schema

NameRequiredDescriptionDefault
imageYesDocker image name to check availability for (e.g. 'csgo', 'nginx')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.3

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds genuinely new behavior: a GAMEYE_API_TOKEN is needed, and without it the tool returns setup steps and sends nothing rather than erroring — a non-obvious degradation path. It stops short of describing pagination or result ordering.

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 tightly packed sentences with zero filler: the capability and its return content come first, the auth precondition second. Every clause carries information an agent would otherwise have to discover by trial.

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 one-parameter read tool with no output schema, the description covers what is returned (regions/datacenters plus ping IPs) and the auth fallback behavior. Only the sibling differentiation against gameye_list_regions is missing from an otherwise complete picture.

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?

With a single parameter at 100% schema coverage, the schema already defines 'image' as a Docker image name with examples. The description reinforces that the image is the thing being checked for hostability but adds no format, casing, or validation detail beyond the schema, so the baseline of 3 applies.

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?

States a specific verb and resource ('Get the list of available regions/datacenters') and scopes it to a given game image, plus mentions ping IPs for latency testing. It does not, however, distinguish itself from the sibling gameye_list_regions, which an agent could easily confuse with this tool.

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 implied by 'that can host a given game image' — i.e., call this when you need image-specific hosting availability rather than a plain region list. There is no explicit when-to-use statement and no named alternative such as gameye_list_regions, so the agent must infer the routing decision.

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