Skip to main content
Glama

Feature Library

Get a recipe for a build

get_recipe
Read-only

Licensed (needs a licence token). The wiring for a scenario: the kit that fits, the steps in order (tier, install, tokens, wiring between the parts, glue, what to build yourself, tone, checks), and for each part you own its pitfalls in full and its guide. Parts you don’t own are listed with their titles, to buy or replace.

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

Input Schema

NameRequiredDescriptionDefault
toneNoOptional tone id.
levelNoHow closely the build follows a look: exact (the look as shipped; the dials and switches only, the default), tuned (also the look’s knobs, in range, then check_look) or inspired (your own look carrying its character; never its name).
platformNoOptional target platform, as for find_parts.
scenarioYesThe build in words, or a kit id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the read-only, closed-world profile, and the description adds meaningfully on top: the licence-token requirement and a fairly detailed account of what comes back, including that parts not owned appear only as titles 'to buy or replace'. It doesn't discuss failure modes, cost of the call, or how large the step list can get.

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?

Effectively one sentence, front-loaded with the licence gate so the agent sees the blocker first. The long parenthetical enumerating step contents is dense but each item carries information; only minor trimming would improve it.

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, single-required-parameter tool with no output schema, the description does the work of explaining the return payload in reasonable detail and flags the licensing gate. Some ambiguity remains about how the recipe differs from sibling retrieval tools, which matters given the crowded namespace.

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 level enum is already fully explained in the schema, so the schema carries the parameter burden. The description hints that 'scenario' accepts a kit id via 'the kit that fits' but adds no format, matching, or fallback details beyond that.

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 concrete resource — the wiring for a scenario — and enumerates its contents (kit, ordered steps, pitfalls, guide), which is far more specific than the title alone. It stops short of naming which sibling to use instead (get_kit, get_playbook, get_shape), so an agent must guess how a 'recipe' differs from a 'kit' or 'playbook'.

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?

It discloses a real prerequisite ('Licensed (needs a licence token)'), which is genuine usage guidance. But there is no statement of when to call this versus get_kit or get_playbook, nor when not to; the appropriate use case is only implied by the 'scenario' input.

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