Skip to main content
Glama

Dockerhub

by io.github.pipeworx-io

Search Images

search_images
Read-onlyIdempotent

Search Docker Hub for container images by keyword. Returns repository name, description, pull count, star count, and official status. Use when finding images for deployment.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of results to return (default 10, max 100)
queryYesSearch query (e.g., "nginx", "postgres")

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
totalYesTotal number of matching repositories
imagesYesList of matching Docker Hub repositories

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "query": "nginx"
+  },
+  {
+    "limit": 25,
+    "query": "postgres"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "images": {
+      "description": "List of matching Docker Hub repositories",
+      "items": {
+        "properties": {
+          "description": {
+            "description": "Short description of the repository",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "is_automated": {
+            "description": "Whether this is an automated build",
+            "type": "boolean"
+          },
+          "is_official": {
+            "description": "Whether this is an official Docker repository",
+            "type": "boolean"
+          },
+          "name": {
+            "description": "Repository name (e.g., namespace/name)",
+            "type": "string"
+          },
+          "pulls": {
+            "description": "Number of pulls",
+            "type": "number"
+          },
+          "stars": {
+            "description": "Number of stars",
+            "type": "number"
+          }
+        },
+        "required": [
+          "name",
+          "description",
+          "stars",
+          "pulls",
+          "is_official",
+          "is_automated"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "description": "Total number of matching repositories",
+      "type": "number"
+    }
+  },
+  "required": [
+    "total",
+    "images"
+  ],
+  "type": "object"
+}
  2. Changed2 schema fields changed
    • removedInput schema / examples
      Removed value: -[
-  {
-    "query": "nginx"
-  },
-  {
-    "limit": 25,
-    "query": "postgres"
-  }
-]
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "images": {
-      "description": "List of matching Docker Hub repositories",
-      "items": {
-        "properties": {
-          "description": {
-            "description": "Short description of the repository",
-            "type": [
-              "string",
-              "null"
-            ]
-          },
-          "is_automated": {
-            "description": "Whether this is an automated build",
-            "type": "boolean"
-          },
-          "is_official": {
-            "description": "Whether this is an official Docker repository",
-            "type": "boolean"
-          },
-          "name": {
-            "description": "Repository name (e.g., namespace/name)",
-            "type": "string"
-          },
-          "pulls": {
-            "description": "Number of pulls",
-            "type": "number"
-          },
-          "stars": {
-            "description": "Number of stars",
-            "type": "number"
-          }
-        },
-        "required": [
-          "name",
-          "description",
-          "stars",
-          "pulls",
-          "is_official",
-          "is_automated"
-        ],
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "total": {
-      "description": "Total number of matching repositories",
-      "type": "number"
-    }
-  },
-  "required": [
-    "total",
-    "images"
-  ],
-  "type": "object"
-}New value: +null
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "images": {
+      "description": "List of matching Docker Hub repositories",
+      "items": {
+        "properties": {
+          "description": {
+            "description": "Short description of the repository",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "is_automated": {
+            "description": "Whether this is an automated build",
+            "type": "boolean"
+          },
+          "is_official": {
+            "description": "Whether this is an official Docker repository",
+            "type": "boolean"
+          },
+          "name": {
+            "description": "Repository name (e.g., namespace/name)",
+            "type": "string"
+          },
+          "pulls": {
+            "description": "Number of pulls",
+            "type": "number"
+          },
+          "stars": {
+            "description": "Number of stars",
+            "type": "number"
+          }
+        },
+        "required": [
+          "name",
+          "description",
+          "stars",
+          "pulls",
+          "is_official",
+          "is_automated"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "description": "Total number of matching repositories",
+      "type": "number"
+    }
+  },
+  "required": [
+    "total",
+    "images"
+  ],
+  "type": "object"
+}
  4. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "query": "nginx"
+  },
+  {
+    "limit": 25,
+    "query": "postgres"
+  }
+]
  5. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint as false, indicating a safe read operation. The description adds details about the return fields and source (Docker Hub), which is helpful but not essential beyond the annotations.

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?

The description is two sentences, each serving a distinct purpose: stating the action and listing return values. It is front-loaded and contains no unnecessary words.

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?

The description covers the main purpose and return fields. With an output schema available, it does not need to detail return values. It is complete enough for a straightforward search tool, though it omits ordering or pagination details.

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

Parameters3/5

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

Schema description coverage is 100%, with both 'query' and 'limit' parameters well-documented. The description mentions 'keyword' but does not add new information beyond the schema, so it meets the baseline of 3.

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 clearly specifies the verb 'Search', the resource 'Docker Hub for container images', and the return fields (repository name, description, pull count, star count, official status). It distinguishes itself from siblings like 'get_image' by being a general search tool.

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?

The description explicitly states 'Use when finding images for deployment', providing a clear use case. While it doesn't mention when not to use or specific alternatives, the context of sibling tools like 'get_image' implies more specific use cases.

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

All Dockerhub toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation2/5

Many tools overlap in purpose, e.g., ask_pipeworx, ask_pipeworx_grounded, deep_research, entity_profile, and validate_claim all perform data lookups with subtle differences. Polymarket tools also have overlapping scopes. The large number of tools with similar functions creates confusion.

Naming Consistency3/5

Names are inconsistent: some use verb_noun (get_image, list_subscriptions), others are descriptive phrases (ai_visibility_check, bet_research), and some are single words (forget, recall). No clear pattern.

Tool Count2/5

33 tools is high, and many are unrelated to Dockerhub. The server name suggests a focused Docker toolset, but the bulk of tools are for Pipeworx/Polymarket/data lookups, making the count excessive for the advertised domain.

Completeness2/5

As a Dockerhub server, it lacks basic Docker operations like push, delete, or manage repositories. As a general data toolset, it covers many domains but still misses some core operations (e.g., no tool for searching inside images).

Resources