Skip to main content
Glama

pdf_create_form_field

Add a text or checkbox form field to a specified PDF page, set its position and size, and save the updated PDF to an output path.

Instructions

Add a new form field (text or checkbox) to a PDF page.

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>",
      "field_name": "<field_name>",
      "field_type": "<field_type>",
      "page": "<page>",
      "x": "<x>",
      "y": "<y>",
      "width": "<width>",
      "height": "<height>",
      "output": "<output>"
    },
    "name": "pdf_create_form_field"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYesX coordinate.
yYesY coordinate.
pageYesPage number.
inputYesThe input PDF file path.
widthYesWidth.
heightYesHeight.
outputYesThe output PDF file path.
field_nameYesField name.
field_typeYesField type.

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 burden of behavioral disclosure and mostly fails to. It does not say whether the input file is modified in place or a new file is written to 'output', what happens if a field with that name exists, or what coordinate origin x/y use. For a write operation with nine required parameters, this leaves the agent guessing about side effects.

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 sentence with zero filler and the action front-loaded. It is efficient, though arguably too terse given the mutation surface, leaving room that could have been spent on the field_type constraint and side effects.

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 nine-parameter, all-required mutation tool with no annotations and no output schema, the definition omits the behaviors an agent most needs: in-place vs. new-file semantics for 'output', overwrite behavior, coordinate conventions, and the accepted field_type values. The purpose is legible but the contract is not.

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 baseline is 3, and the schema's per-parameter descriptions are terse labels like 'Field type.' and 'Page number.' The one genuine addition is constraining field_type to text or checkbox, since the schema provides no enum; the remaining eight parameters gain no meaning from the description.

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 ('Add a new form field ... to a PDF page') and narrows the field kinds to text or checkbox, which separates it from siblings like pdf_fill_form and pdf_read_form. It stops short of explicitly naming those siblings, so an agent must infer the distinction from the verb alone.

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 choose this tool over pdf_fill_form or pdf_read_form, and no stated prerequisites such as whether the source PDF must already contain an AcroForm. The only implicit cue is that this tool creates a field while the siblings consume or fill them.

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