Skip to main content
Glama

Docker Recipes

Search recipes

search_recipes
Read-only

Search Docker Compose recipes by keywords (app name, technology, use case). Returns ranked matches with slug, title, description and URLs.

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": {
      "query": "<query>"
    },
    "name": "search_recipes"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (default 10)
queryYesKeywords, e.g. 'postgres pgadmin' or 'media server'
categoryNoLimit to one category slug
difficultyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and locality are covered. The description still adds real value by disclosing the return contract ('ranked matches with slug, title, description and URLs'), which matters because there is no output schema. It omits pagination/ranking mechanics, keeping it off a 5.

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?

Two sentences, zero filler. The matching behavior is front-loaded and the return shape follows immediately, which is exactly the order an agent needs.

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 read-only search tool with no output schema, the description covers both what goes in (keywords, matching dimensions) and what comes out (ranked fields). Only ranking behavior across categories/difficulty and result-window semantics are left unstated.

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 75% and the schema already supplies query examples, the default limit of 10, and enumerated category values. The description only echoes the keyword notion and adds nothing about difficulty or how multiple keywords combine, so it neither compensates for the one undocumented parameter nor exceeds the schema.

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 names a specific verb and resource ('Search Docker Compose recipes') and scopes it to keyword matching over app name, technology and use case. That distinguishes it in practice from siblings like list_recipes and get_recipe, though it never names them, so it stops short of a 5.

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?

The phrase 'by keywords' plus example query shapes implies when to use it (you have search terms rather than a known slug), but there is no explicit when-not guidance and no routing to list_recipes or list_categories for browsing. Usage is inferred rather than stated.

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