Skip to main content
Glama

document_workflow

Run declarative multi-step PDF workflows from presets or TOML/JSON recipes, transforming an input document into a specified output file.

Instructions

Execute a declarative multi-step document workflow pipeline

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>",
      "output": "<output>"
    },
    "name": "document_workflow"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYesPath to input PDF file
outputYesPath to output PDF file
presetNoPreset workflow ID (e.g. preset-legal-discovery, preset-clean-scan, preset-redact-protect)
recipeNoPath to TOML .ppflow / JSON recipe, raw JSON, or multiline TOML
name_templateNoOptional basename template; output is then a directory

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden. It says nothing about whether the output file is overwritten, whether steps are transactional or partially applied on failure, what permissions are needed, or how execution status is reported — all critical for a multi-step executor.

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 wasted words, which is good structure. The terseness, however, leaves the description under-specified rather than genuinely concise in a helpful sense.

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?

This is a complex, five-parameter execution tool with no annotations and no output schema, yet the definition is one abstract sentence. An agent needs to know how presets and recipes combine, whether execution is destructive, and how to retrieve results; none of that is present.

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 description coverage is 100%, so input, output, preset, recipe, and name_template are already documented with examples in the schema. The description adds no meaning beyond that — notably no explanation of the interaction between preset and recipe or when name_template turns the output into a directory. Baseline 3 applies when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a verb and a resource ("Execute ... workflow pipeline"), and "declarative multi-step" hints at the concept, but the resource stays abstract — it never says the pipeline operates on PDFs (input/output PDF paths) or what a workflow can actually do. An agent cannot tell from this sentence how it differs from siblings like document_pii_scan or list_workflows.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance: nothing says when to pick a preset versus a recipe, or when this tool should be chosen over the many single-purpose PDF siblings. The agent must infer that this is the orchestration entry point.

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