Skip to main content
Glama

cli_fill_batch

Batch-fills AcroForm PDFs from CSV/JSON or supplied records, producing populated PDFs and machine-readable receipts for verification.

Instructions

Automated batch AcroForm fill engine generating populated PDFs and machine-readable receipts.

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

C2.4/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It discloses only that output includes populated PDFs and machine-readable receipts; it says nothing about overwrite behavior in output_dir, partial-failure handling, permission requirements, or whether filling is reversible or keeps forms editable.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single front-loaded sentence with no wasted words, but it is under-specified rather than appropriately concise for a tool with eight parameters and batch semantics.

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?

For a complex batch mutation tool with eight parameters, low schema coverage, no annotations, and no output schema, this one-line description is not complete enough. It names outputs but does not explain required inputs, validation rules, or operational behavior.

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

Parameters1/5

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

Schema description coverage is only 25%, and six of the eight parameters—including template, field_map, output_dir, keep_editable, and name_template—have no description in the schema. The description adds no parameter-level meaning to compensate.

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?

The description states a specific verb and resource: a batch AcroForm fill engine that produces populated PDFs and receipts. It is clear what the tool does, but it does not differentiate itself from likely siblings such as batch_fill or pdf_fill_form.

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 guidance on when to use this tool versus alternatives, no prerequisites, and no indication of when not to use it. The single sentence describes capability but leaves all routing decisions to inference.

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