Skip to main content
Glama

pdf_fill_form

Fill AcroForm fields in a PDF using supplied values, saving the completed document to a new output PDF file for reliable form submission.

Instructions

Fill AcroForm fields in a PDF. [Input: PDF (.pdf) | Output: PDF (.pdf)]

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

Input Schema

NameRequiredDescriptionDefault
inputYesThe input PDF file path.
outputYesThe output PDF file path.
valuesYesValues to fill.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/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 disclosure burden, yet it says nothing about whether existing field values are overwritten, whether the form is flattened, what happens when a supplied field name does not exist, or whether output paths are overwritten. The only behavioral content is the input/output format bracket.

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?

The purpose sentence is front-loaded and free of waste, and the bracketed format tag is compact. The second sentence is somewhat boilerplate but adds useful file-type expectations in minimal space.

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 mutation tool with a nested values object, no annotations, and no output schema, the description is thin. It leaves unanswered how field names are keyed in 'values', what errors occur for missing fields, and what the caller gets back, all of which an agent needs to invoke it reliably.

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 the three parameters are already documented in the schema and the baseline of 3 applies. The description adds no meaning beyond it, and notably says nothing about the nested 'values' object, where field-name-to-value mapping is non-obvious.

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 gives a specific verb and resource: 'Fill AcroForm fields in a PDF', which is concrete enough that an agent knows exactly what operation occurs. It does not differentiate from related siblings such as pdf_read_form, pdf_create_form_field, or batch_fill, so it stops short of 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 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, no exclusions, and no mention of alternatives. An agent is not told that the PDF must already contain AcroForm fields (versus using pdf_create_form_field first) or when batch_fill would be the better choice for multiple documents.

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