Skip to main content
Glama

devops-linux

docker_image_manifest_inspect

Inspect OCI / Docker image manifest.json or config JSON to report layer digests, total size, entrypoint, exposed ports, and env keys.

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

Input Schema

NameRequiredDescriptionDefault
textNo
filePathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the analysis outputs (digests, size, entrypoint, ports, env keys), which gives useful signal, but it never states that this is a read-only parse, what happens on malformed input, or how the two input modes behave.

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?

One sentence, front-loaded with the action and resource, followed by the concrete outputs. No filler or redundant restatement of the name.

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?

For a small two-parameter inspection utility with no output schema, the description adequately conveys what the tool returns. Its main shortfall is the uninformed input handling, which is a minor but real gap given zero schema documentation.

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 neither parameter is mentioned in the description. The description never explains the distinction between supplying raw manifest 'text' and a 'filePath', which is the single most important invocation decision for this tool.

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 uses a specific verb ('Inspect') plus a precise resource ('OCI / Docker image manifest.json or config JSON') and enumerates the reported fields (layer digests, total size, entrypoint, exposed ports, env keys). That is enough to separate it from siblings like dockerfile_lint or docker_run_to_compose, though no sibling is named explicitly.

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 only implied by the resource and the listed outputs; there is no explicit statement of when to choose this tool over alternatives, nor any prerequisite or exclusion guidance. An agent can infer intent but must guess at boundaries.

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