Skip to main content
Glama

Recipe Validate

recipe_validate
Read-only

Validate a recipe reference and its inputs without building to catch unknown recipes, missing required inputs, and invalid parameter types, ranges, or units.

Instructions

Validate a recipe reference {recipe, inputs} WITHOUT building it — the cheap front door (mirrors validate_manifest). Catches an unknown recipe, a missing required input, and a wrong-typed / out-of-range / bad-unit / unknown input. Returns {ok, problems} — ok is True iff problems is empty. Run before building or merging to reject a malformed parameterization before geometry is spent.

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_validate"
  }
}

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

A4.7/5.0
Behavior5/5

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

Beyond readOnlyHint=true, it discloses the exact failure classes checked (unknown recipe, missing required input, wrong-typed / out-of-range / bad-unit / unknown input) and the return contract ({ok, problems}, ok iff problems empty) even though no output schema exists. This is substantive behavior the annotations do not carry.

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?

Four short sentences, front-loaded with the verb and the 'without building' qualifier, followed by checks, return contract, and directive. No filler sentences.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 3-param read-only validator with no output schema, the description covers purpose, checks performed, return shape, and when to invoke it. Nothing an agent needs to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 33% (only `workspace` is documented), so the description must compensate: it names `recipe` as a reference and `inputs` as the parameterization, and characterizes what about inputs is checked (missing, wrong-typed, out-of-range, bad-unit, unknown). It stops short of describing the shape of the inputs object, but adds real meaning over the bare schema.

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?

States a specific verb and resource ('Validate a recipe reference {recipe, inputs}') plus the key scoping fact that it does so 'WITHOUT building it'. The parenthetical 'mirrors validate_manifest' and the contrast with actually building/merging cleanly separate it from the sibling `recipe` tool.

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?

Explicitly says when to call it: 'Run before building or merging to reject a malformed parameterization before geometry is spent.' The alternative (building/merging) is named implicitly, though no explicit when-not or pointer to the `recipe`/`recipe_schema` tools is given.

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