Skip to main content
Glama

Check image tag

gameye_check_tag
Read-onlyIdempotent

Verify a Docker image tag is deployed to a specified Gameye region before launching a session, confirming the version is available.

Instructions

Verify that a specific Docker image tag has been deployed to a given region in the Gameye fleet. Use this before launching a session to confirm the version is available. 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": {
      "region": "<region>",
      "image": "<image>",
      "version": "<version>"
    },
    "name": "gameye_check_tag"
  }
}

Input Schema

NameRequiredDescriptionDefault
imageYesDocker image name (e.g. 'csgo', 'tf2')
regionYesRegion/location to check (e.g. 'europe', 'us-east')
versionYesDocker image tag/version to verify (e.g. '1.2.3', 'latest')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.3

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered elsewhere. The description adds genuine value beyond that: it requires GAMEYE_API_TOKEN and, when the token is missing, returns setup steps and sends nothing, which is a non-obvious failure mode worth surfacing. It does not say what a successful check returns (boolean, list of regions, etc.), leaving the primary outcome opaque.

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?

Three sentences, front-loaded with the purpose before the usage hint and the auth caveat, with no filler. The sequencing is sensible: what it does, when to call it, what can go wrong. Slight deduction for the auth sentence reading as a footnote rather than being integrated with usage.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

It is a simple read-only tool with three fully documented required params and no output schema, so the description is close to sufficient. The notable gap is the result: an agent cannot tell whether a successful call returns a boolean, a list of regions, or available tags, and for a verification tool that is the core information.

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 100%, and each of the three required parameters (image, region, version) already carries an example in its schema entry. The description adds only the framing that region refers to a location in the Gameye fleet; it offers no further syntax or constraint detail beyond the schema, so the baseline 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?

The description gives a specific verb and resource: 'Verify that a specific Docker image tag has been deployed to a given region in the Gameye fleet.' That is far more informative than the title 'Check image tag'. It does not, however, explicitly distinguish itself from near neighbors like gameye_list_registry_tags or gameye_enable_tag, so an agent still has to infer the boundary from sibling names alone.

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

Usage Guidelines4/5

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

'Use this before launching a session to confirm the version is available' gives a concrete trigger and names the downstream action (launching a session), which is a real usage signal. It stops short of stating when not to use it, or which sibling to choose for listing or enabling tags instead.

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