Skip to main content
Glama

recipe_run

Run a .ppflow recipe against a local PDF in a single one-shot execution, producing the configured output without starting a daemon.

Instructions

Execute a .ppflow recipe against a local PDF file immediately (one-shot, no daemon).

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

Input Schema

NameRequiredDescriptionDefault
inputYesAbsolute path to input PDF
outputNoOutput file, or output directory with name_template
recipeYesAbsolute path to .ppflow TOML recipe file
name_templateNoOptional dynamic output basename; requires explicit output directory

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description must carry the full behavioral burden. It usefully discloses the one-shot, daemonless execution model and that input is a local file, but it says nothing about whether output files are overwritten, what permissions or side effects apply, or what happens on recipe failure.

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?

A single front-loaded sentence with the verb and resource first and the execution-model qualifier second. Nothing is redundant or 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?

For a four-parameter tool with fully documented schema and no output schema, the description covers what the tool does and how it runs. The remaining gap is post-execution behavior (overwrite semantics, failure reporting), which is meaningful but secondary given the complete 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%, so the schema already documents all four parameters including the name_template/output-directory relationship. The description only reinforces 'local PDF' and adds no format, syntax, or constraint detail beyond the schema, so the baseline of 3 applies.

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 ('Execute') and resource (a .ppflow recipe applied to a local PDF), and the parenthetical clarifies the execution model. It is distinguishable from sibling converters like md_to_pdf, though it never names a concrete alternative such as document_workflow or batch_fill.

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 phrase 'immediately (one-shot, no daemon)' implies this is for single ad-hoc runs rather than persistent/scheduled processing, which is useful implied usage guidance. However, there is no explicit when-to-use/when-not statement and no named alternative for batch or daemon-style execution.

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