Skip to main content
Glama

Build Recipe

recipe

Builds a registered part definition into the active document by validating typed inputs against its schema, then executing deterministic geometry, interface, and intent steps.

Instructions

Build a registered part recipe into the active document (issue #136): "regenerate with new parameters" = "re-run the recipe." Validates {recipe, inputs} against the declared schema (typed units + ranges) at the door, then runs the deterministic build — geometry + publish_interface + declare_intent. Returns {recipe, schema, inputs, handle, name, interfaces, intent, part}.

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

Input Schema

NameRequiredDescriptionDefault
inputsNo
recipeYes
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

A3.6/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false / destructiveHint=false / openWorldHint=false; the description goes well beyond by disclosing that inputs are schema-validated at the door with typed units and ranges, that the build is deterministic, and that it mutates the document via geometry, publish_interface, and declare_intent. It does not say what happens to pre-existing geometry or whether re-runs overwrite, which is the remaining gap for a write tool.

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

Conciseness3/5

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

Purpose and effects are front-loaded, which is good, but the '(issue #136)' tracker reference and the quoted 'regenerate with new parameters' quip consume space without helping an agent decide or call. The single dense run-on sentence also makes the validation and build phases harder to parse.

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?

With no output schema, the description usefully enumerates the return payload {recipe, schema, inputs, handle, name, interfaces, intent, part}, and annotations cover the safety profile, so an agent has enough to invoke it. The missing piece is failure behavior and workspace scoping, which the 33% schema coverage leaves undocumented.

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 33% — only `workspace` is documented in the schema. The description does add real meaning for `inputs` by tying its shape to the recipe's declared schema (typed units + ranges), which the bare `additionalProperties: true` object does not convey. However, `workspace` is never mentioned, and the `recipe` identifier format (name vs. handle vs. path) is left ambiguous.

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?

States a specific verb and resource: build a registered part recipe into the active document, and spells out the resulting side effects (geometry + publish_interface + declare_intent). This clearly separates it from recipe_list/recipe_schema, though it never explicitly names recipe_validate as the validation-only alternative, so sibling differentiation is only implied.

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 gloss '"regenerate with new parameters" = "re-run the recipe"' gives a real usage scenario, and 'into the active document' implies prerequisites (a document must be active). But there is no explicit when-to-use vs. when-not, and the near siblings recipe_validate and recipe_schema are never mentioned as alternatives.

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