Skip to main content
Glama

List local images or search a registry

nas_docker_images
Read-only

List and filter local Docker images by name or status, and search a remote registry, to identify unused images by size for cleanup.

Instructions

source "local" (default) lists the images stored on the NAS (data.result[]), optionally filtered by name or status and sorted; image_size is a string holding bytes. To find what can be cleaned up, filter status "unused" and sort by size. source "registry" searches the remote image registry for name (data.search_image[]) and supports page and page_size. Images cannot be deleted through this server; the user has to do that in the Docker app on the NAS.

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

Input Schema

NameRequiredDescriptionDefault
nameNoName filter for "local"; the search term (required) for "registry".
pageNo"registry" only: page number.
orderNoSort direction.
sourceNoImages on the NAS, or the remote registry.local
statusNo"local" only: image states.
sort_byNo"local" only: sort key.
page_sizeNo"registry" only: results per page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuine value beyond that: it discloses the response paths (data.result[] vs data.search_image[]), that image_size is a string of bytes, and that deletion is out of scope and must be done in the Docker app on the NAS.

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?

The text is front-loaded by mode, one clause per source, followed by a practical tip and a limitation, with no filler sentences. It reads as a dense run-on in places but every clause carries operational 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 no output schema and seven parameters, the description carries the burden of explaining return structure and does so by naming data.result[] and data.search_image[] field paths. Combined with the mode split, default source, and deletion limitation, an agent has everything needed to invoke it 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% and the schema already marks page/page_size as registry-only and status/sort_by as local-only, so the baseline is 3. The description still adds meaning by explaining the data type of image_size and by pairing status "unused" with sort_by size as a recommended combination, which is not 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?

The description names the resource precisely ('images') and splits it into two explicit modes: source "local" lists images stored on the NAS, source "registry" searches the remote registry. An agent can immediately tell this apart from sibling tools dealing with containers, projects, or app usage.

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?

It gives a concrete recipe for a real task ('To find what can be cleaned up, filter status "unused" and sort by size') and states the default source. It also rules out a tempting but impossible action ('Images cannot be deleted through this server'), though it does not name any sibling alternative for related image/app queries.

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