Skip to main content
Glama

Recipe List

recipe_list
Read-only

Browse all registered part recipes to view available build templates, their required and optional inputs, and emitted outputs before selecting and parameterizing one.

Instructions

List every registered part recipe — named, parameterized, declared-input build templates (issue #136). Returns {schema, count, recipes} where each recipe maps to {doc, required, optional, emits}; the cheap directory to browse before picking and parameterizing a recipe with recipe_schema / recipe.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "recipe_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspaceNoRun this call in this named workspace

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.7
    • addedInput schema / properties / workspace
      Added value: +{
      +  "default": "",
      +  "description": "Run this call in this named workspace",
      +  "title": "Workspace",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.1/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 is covered. The description adds real value beyond them by spelling out the exact response shape ({schema, count, recipes} with per-recipe {doc, required, optional, emits}) and characterizing the call as 'cheap'. No contradictions with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One front-loaded sentence that leads with the action and ends with the routing advice, with no wasted lines. It's dense – the return-shape clause and the '(issue #136)' reference add clutter – but nothing is padded.

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?

No output schema exists, and the description compensates by describing the return object and per-recipe fields, which is the main thing an agent needs for a read-only listing tool. Only the workspace scoping nuance is left to the schema.

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 coverage is 100% and the single optional 'workspace' parameter is fully documented there, so the description needn't repeat it. The description adds no syntax or scoping detail about the workspace beyond the schema, which is baseline-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?

A specific verb+resource ('List every registered part recipe') plus a definition of what a recipe is ('named, parameterized, declared-input build templates'). It explicitly distinguishes this tool from the parameterizing siblings recipe_schema and recipe, and even documents the return shape, so an agent knows exactly what it is enumerating.

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 phrase 'the cheap directory to browse before picking and parameterizing a recipe with recipe_schema / recipe' names the alternatives and the ordering, which is strong routing guidance. It doesn't state explicit exclusions (e.g., when not to enumerate the full list), so it falls short of the top mark.

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

Deploy Server

Other Tools