Skip to main content
Glama

Render a StewAI Recipe Build

render_recipe_build
Read-onlyIdempotent

Render one private recipe build with optional fixture values without executing it.

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

Input Schema

NameRequiredDescriptionDefault
fixturesNo
build_refYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world, so the safety profile is covered. The description adds a genuine behavioral claim beyond them — that no execution occurs — plus a 'private' scope note, but says nothing about permissions, cost, or what rendering actually resolves.

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?

A single front-loaded sentence with no filler; the key constraint (no execution) is stated up front. It is dense but slightly under-explanatory, with 'private' left unelaborated.

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

Completeness2/5

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

An output schema exists, so return values needn't be described. But the tool's core ambiguity is unresolved: what 'render' yields (resolved spec, expanded config, diagnostics?) versus a check or preflight, and how the required build_ref is obtained. For a build-scoped tool in a dense sibling set, that gap is material.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry parameter meaning. It only gestures at 'optional fixture values' (mapping loosely to the fixtures object) and says nothing about build_ref, the single required identifier, nor about the fixtures shape or limits.

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?

Uses a specific verb-plus-resource ('Render one private recipe build') and states an important negative scope ('without executing it'), which separates it from execution-oriented siblings. It stops short of distinguishing itself from adjacent read/review tools like preflight_recipe_build or check_recipe_build, and leaves 'render' itself undefined.

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?

'Without executing it' implies a dry-run/preview use case, so the agent can infer when this is appropriate. However, there is no explicit when-to-use/when-not guidance and no named alternative among the many recipe-build siblings that also inspect a build.

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