Skip to main content
Glama

Docker Recipes

Get recipe

get_recipe
Read-only

Get one recipe as Markdown: overview, docker-compose.yml, .env template, prerequisites, usage notes and troubleshooting.

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": {
      "slug": "<slug>"
    },
    "name": "get_recipe"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesRecipe slug from search_recipes, e.g. 'postgresql'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Beyond the 'readOnly' annotation, the description is highly transparent about the content and format of the result, detailing specific components like docker-compose.yml and prerequisites within the Markdown output.

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 extremely concise, using a colon structure to front-load the core purpose and list all return components without any unnecessary filler.

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?

Given that it has no output schema, the description is highly complete, providing a full blueprint of the expected response structure and content for the agent.

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?

Since schema coverage is 100%, the description adds minimal value beyond providing an example format for the slug. It confirms the input requirement but doesn't add critical semantic meaning beyond what the schema already defines.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it retrieves a single recipe but focuses on the output content (Markdown structure) rather than making an explicit distinction from siblings like `list_recipes`.

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?

Usage is implied by the requirement of a 'slug' (which suggests the recipe must first be found via a search or listing), but there is no explicit guidance on when to use this tool versus others.

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