Skip to main content
Glama

devops-linux

dockerfile_lint

Lint a Dockerfile against security and build-cache best practices (latest tags, root USER, apt cache cleanup, ADD vs COPY, HEALTHCHECK, exposed secrets).

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": "dockerfile_lint"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNo
filePathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the substantive behavior: the specific rule categories it checks, implying a static read-only analysis. However, it says nothing about whether it mutates or writes anything, whether it needs network access or a Docker daemon, or what form the findings take — gaps that matter for a tool with zero annotation coverage.

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?

A single front-loaded sentence with the verb first and the rule list as a compact parenthetical; every clause adds information and there is no filler or repetition.

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

Completeness2/5

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

The domain purpose is well covered, but with no annotations, no output schema, and 0% parameter coverage, the definition leaves the caller unsure how to actually invoke it (inline text vs file path) and what to expect back. For a two-input tool whose inputs are entirely undocumented elsewhere, more was needed.

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 description coverage is 0% and the description never mentions the two parameters at all. It gives no clue whether to supply inline 'text' or a 'filePath', or how precedence works when both or neither are provided (required count is 0), so it does not compensate for the schema gap.

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 ('Lint a Dockerfile') and enumerates the check categories (latest tags, root USER, apt cache cleanup, ADD vs COPY, HEALTHCHECK, exposed secrets), which clearly separates it from siblings like docker_image_manifest_inspect or docker_run_to_compose.

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 the name and by the enumerated rules — you run it to audit a Dockerfile — but there is no explicit when-to-use/when-not guidance, no statement about prerequisites, and no named alternative for related tasks in the sibling set.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources