Shipshape MCP server

lint

Read-onlyIdempotent

Checks Dockerfiles and Kubernetes manifests for security and configuration issues, returning grade, score, pass/fail status, and findings with line-level fixes.

Instructions

Lint a Dockerfile or Kubernetes manifest. Returns the grade, score, passed and every finding with its line, fix and reference. Give either content or path.

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

Input Schema

Name	Required	Description	Default
`path`	No	A local file to lint instead of `content`.
`type`	No	auto detects Dockerfile vs Kubernetes YAML/JSON.	auto
`ignore`	No	Rule ids to skip, e.g. ["DF-017"].
`content`	No	The Dockerfile or manifest, as text (up to 512 KiB).
`fail_on`	No	`passed` is false at this severity or worse.	high

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.2Nov 5, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so safety is covered. The description adds genuinely new behavior: the exact shape of the result (grade, score, `passed`, findings with line, fix and reference), which an agent cannot get from the annotations and which tells it what it will have to parse. It does not state what happens when both or neither input is supplied.

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?

Three short sentences, zero filler. The action and target come first, the return payload second, and the input constraint last, so the reader gets the essentials in reading order.

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?

With no output schema, the description fills that void by enumerating the return fields, and the schema covers the rest of the parameters. The only missing piece is the edge case of conflicting or absent `content`/`path`, which is minor but leaves an agent guessing on an unconstrained parameter set.

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 description coverage is 100%, so the schema already explains `type`, `ignore`, `fail_on` and the size cap. The description still adds meaning beyond it by declaring `content` and `path` mutually exclusive, a constraint the schema does not express (both simply default to null with no oneOf). That is real value on top of an already documented 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 and two concrete resources ("Lint a Dockerfile or Kubernetes manifest") and immediately scopes the return payload to grade, score, passed and findings. There are no sibling tools to disambiguate from, so the definition is fully self-sufficient for selection.

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?

The only usage instruction is "Give either `content` or `path`," which is input-shape guidance rather than when-to-use guidance. There are no alternatives to route between, so the gap is small, but no context is given for choosing inline content versus a file path.

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

Deploy Server

Other Tools

lintA