Skip to main content
Glama

get_dockerhub_repo

Get public metadata for a Docker Hub image repository: description, stars, pull count, last updated.

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": {
      "repository": "<repository>"
    },
    "name": "get_dockerhub_repo"
  }
}

Input Schema

NameRequiredDescriptionDefault
repositoryYese.g. nginx or bitnami/redis

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations provided, the description carries the full behavioral burden. It usefully signals that the metadata is public, implying no authentication is required for these reads, but it does not disclose rate limits, error behavior for missing repositories, or whether the call is strictly read-only beyond the verb 'Get'.

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 definition is a single front-loaded sentence with no filler. Every clause earns its place by naming the resource, the public/read nature, and the returned fields.

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 simple one-parameter read tool with complete schema coverage and no output schema, the description is nearly sufficient: it names the source, access level, and returned fields. Minor gaps remain around error cases and rate limits, but nothing critical to correct invocation is missing.

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%, so the single repository parameter is already documented with an example format ('nginx or bitnami/redis'). The description adds no extra parameter semantics beyond confirming it takes an image repository, so baseline 3 is appropriate.

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 states a specific verb (Get) and resource (public metadata for a Docker Hub image repository), and it enumerates the exact fields returned: description, stars, pull count, last updated. This makes the tool's purpose immediately distinguishable from the sibling get_app_store_reviews by domain.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains what the tool does but gives no guidance on when to use it versus alternatives, no prerequisites, and no exclusions. The only sibling is get_app_store_reviews, but the description does not mention routing logic or context for choosing between them.

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