Skip to main content
Glama

batch_fill

Fill AcroForm PDF templates in batch from CSV, JSON paths, or inline records, returning per-row results and a receipt; outputs are flattened by default and never overwritten.

Instructions

Fill a local AcroForm PDF from a CSV/JSON path or inline JSON records; returns per-row results and a persisted receipt. Flattens by default and never overwrites outputs.

Input Schema

NameRequiredDescriptionDefault
dataNoLocal .csv or .json data path
dateNoOptional YYYY-MM-DD UTC date override
recordsNo
templateYes
field_mapNo
output_dirYes
keep_editableNo
name_templateNo{index:04}.pdf

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/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, and it does disclose two useful traits: outputs are flattened by default and existing outputs are never overwritten, plus it returns a persisted receipt. It leaves open what actually happens on a filename collision (skip vs. error), whether the template is modified, and how partial per-row failures are reported, which matters for a batch mutation.

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?

Two tight sentences, front-loaded with the primary action and immediately followed by return-value and safety behavior. No filler or redundant restatement of the name.

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

Completeness3/5

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

The output side is adequately covered ('per-row results and a persisted receipt'), compensating for the missing output schema. But for an 8-parameter batch tool with no annotations and 25% schema coverage, several parameters and failure modes remain unexplained, leaving the definition only partially complete.

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 only 25% (template, output_dir, field_map, name_template, date, keep_editable are undocumented in the schema), so the description has to compensate. It clarifies that 'data' and 'records' are two alternative input routes and that flattening is the default, but field_map, name_template, date, and output_dir semantics are never explained.

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?

Names a specific verb and resource ('Fill a local AcroForm PDF') and enumerates the accepted input modes (CSV/JSON path or inline JSON records), which is enough for an agent to distinguish it from a single-form filler such as pdf_fill_form. It stops short of explicitly contrasting itself with any sibling, so a 4 rather than a 5.

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?

Usage is only implied: the presence of 'batch' and a data source suggests multi-row filling, and the word 'local' hints at a local-file prerequisite. There is no explicit when-to-use, when-not-to-use, or pointer to cli_fill_batch/pdf_fill_form as the single-record alternatives.

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