Skip to main content
Glama
aserper

RTFD (Read The F*****g Docs)

by aserper

search_docker_images

Find Docker container images on DockerHub by name or keywords to discover official and community images for specific services, applications, or technologies.

Instructions

        Search for Docker images on DockerHub by name or keywords.

        USE THIS WHEN: You need to find Docker container images for a specific service, application, or technology.

        BEST FOR: Discovering official and community Docker images.
        Returns multiple matching images with names, descriptions, star counts, pull counts, and whether they're official.

        After finding an image, use:
        - docker_image_metadata() for detailed information
        - fetch_docker_image_docs() for README and usage instructions
        - fetch_dockerfile() to see how the image is built

        Args:
            query: Search query (e.g., "nginx", "postgres", "machine learning", "python")
            limit: Maximum number of results (default 5)

        Returns:
            JSON with list of matching images including name, description, stars, pulls, official status

        Example: search_docker_images("postgres") → Finds official postgres image and alternatives
        

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
limitNo
Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses that the tool returns multiple matching images with specific attributes (names, descriptions, star counts, etc.) and mentions it searches DockerHub. However, it doesn't cover potential rate limits, authentication needs, or error behaviors, leaving some gaps for a search tool.

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 well-structured with clear sections (purpose, usage guidelines, parameter details, returns, example) and every sentence adds value. It's appropriately sized without redundancy, making it easy to scan and understand.

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?

Given no annotations and no output schema, the description provides comprehensive context: purpose, usage guidelines, parameter semantics, return format, and an example. It covers all necessary aspects for a search tool with two parameters, making it complete enough for effective use.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must compensate. It clearly explains both parameters: 'query' as a search query with examples and 'limit' as maximum results with default value. This adds meaningful context beyond the bare schema, fully documenting the parameters.

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 states the tool searches for Docker images on DockerHub by name or keywords, specifying the verb 'search' and resource 'Docker images'. It distinguishes from siblings like docker_image_metadata (detailed info) and fetch_dockerfile (build details) by focusing on discovery.

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

Usage Guidelines5/5

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

The description includes explicit 'USE THIS WHEN' and 'BEST FOR' sections, stating to use it for finding images for specific services/applications and discovering official/community images. It also lists alternative tools to use after finding an image, providing clear guidance on when to use this vs. other tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/aserper/RTFD'

If you have feedback or need assistance with the MCP directory API, please join our Discord server