Skip to main content
Glama

Check Dockerfile

gameye_check_dockerfile
Read-onlyIdempotent

Validates a game server Dockerfile against the Gameye container contract offline, flagging port, launch, user, and credential issues with severity, line, and fix guidance.

Instructions

Works without a Gameye account or token. Check game server Dockerfile text against the gameye-containerize container contract, offline: linux/amd64 base, exposed ports and protocols, exec-form launch without npm/yarn start, no loopback bind, non-root user, and no API token or credential in ENV/ARG. Returns findings with severity, rule code, line, message and fix, plus what the check cannot know. Pass the Dockerfile text itself; this tool reads no files 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": {
      "dockerfile": "<dockerfile>"
    },
    "name": "gameye_check_dockerfile"
  }
}

Input Schema

NameRequiredDescriptionDefault
portsNoOptional: the ports and protocols the server binds, to check against EXPOSE
dockerfileYesThe full Dockerfile text (not a path)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.3

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered structurally. The description still adds real value by stating it runs fully offline, reads no files, sends nothing, and reports 'what the check cannot know' — genuine disclosure of limitations beyond the annotations. However it does not detail failure mode (e.g. malformed input) or severity semantics, keeping it at a solid 4-level contribution.

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 sentences, front-loaded with the offline/credential-free fact and then the rule set, ending with a precise statement of the return shape. No filler and no repetition of the title.

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?

With no output schema, the description does the right thing by enumerating the finding fields (severity, rule code, line, message, fix) and noting unknown-unknowns. Combined with the full schema coverage and rich annotations, an agent has enough to call it correctly. Only the optional ports parameter's effect on results is left implicit.

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 coverage is 100% with the dockerfile param already described as 'The full Dockerfile text (not a path)', so the description's 'Pass the Dockerfile text itself; this tool reads no files' largely restates the schema. The mention of 'exposed ports and protocols' hints at the optional ports parameter's role but never explains it directly. Baseline 3 is appropriate when the schema does the heavy lifting.

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 resource ('Check game server Dockerfile text against the gameye-containerize container contract') and pins the scope with 'offline'. The enumerated rule list (base image, EXPOSE, exec-form launch, loopback bind, non-root user, secrets) makes its remit unmistakable and distinct from any other gameye_* tool.

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?

Gives clear operating context: 'Works without a Gameye account or token' and 'Pass the Dockerfile text itself; this tool reads no files and sends nothing' tell the agent exactly what input to supply and what prereqs are unnecessary. It stops short of explicit when-not-to-use guidance or naming a sibling check tool as an alternative, so it falls just below a 5.

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