Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

Lint a Dockerfile for security and size issues: check a Dockerfile for security problems and image size issues

dockerfile_lint
Read-only

Check a Dockerfile (up to 8,000 characters) for common security and image-size problems: unpinned or :latest base images, running as root, piping downloads into a shell, sensitive values baked into ENV or ARG, ADD from URLs, apt and pip cache left in layers, sudo, chmod 777 and an exposed SSH port. Returns each finding with its line, a severity and a fix, plus a score. Use before building or shipping an image. Example: dockerfile=FROM node:latest COPY . /app CMD node /app/server.js. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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

Input Schema

NameRequiredDescriptionDefault
dockerfileYesDockerfile contents (up to 8,000 characters)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=true, destructiveHint=false), the description discloses the 8,000-character input ceiling, the finding structure (line, severity, fix, plus a score), and the charging model: $0.01/call, first 25 free, failed calls free, and repeats are not free. The repeat-charge note meaningfully explains the non-idempotent behavior flagged by idempotentHint=false, and it explicitly confirms nothing is mutated.

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?

Front-loaded with purpose and the concrete check list, followed by use case, example, and pricing in a logical order. The multi-line inline example plus the pricing sentences make it a bit longer than strictly necessary, but every sentence carries information.

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

Completeness5/5

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

With one simple parameter and no output schema, the description still covers input constraints, what is returned (per-finding line/severity/fix and an aggregate score), and cost semantics. An agent has everything needed to call it and interpret results correctly.

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

Parameters4/5

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

Schema coverage is 100% for the single parameter, so the schema already documents it; the description reinforces the 8,000-character limit and clarifies via example that the value is raw Dockerfile text, not a path or repo reference. That distinction (contents vs. file location) is genuinely useful and not stated in the schema.

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 (check/lint) and resource (a Dockerfile), and enumerates exactly which problems are detected (unpinned/:latest base images, root user, curl|sh, secrets in ENV/ARG, ADD from URLs, apt/pip cache, sudo, chmod 777, SSH port). Nothing in the sibling list overlaps, so an agent can route confidently.

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 before building or shipping an image" gives a clear timing/context cue for invocation. There are no exclusion rules or named alternatives, but no sibling tool performs Dockerfile linting, so there is nothing meaningful to disambiguate against.

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.