Skip to main content
Glama
Sign In

PDFOven

by com.pdfoven
OverviewDiscussionsAdmin

Fill PDF form

fill_pdf_form
Idempotent

Fill a PDF form's fields by name (text, checkboxes as true/false, radio and dropdown options) and optionally flatten it so it can't be edited. Unknown field names are an error with suggestions. Uses one render.

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": {
      "file": "<file>",
      "fields": "<fields>"
    },
    "name": "fill_pdf_form"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYesThe PDF form.
fieldsYesField name to value: string, number, boolean, or a list for multi-select fields.
strictNoDefault true. False skips unknown field names.
flattenNoMake the filled form read-only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnly=false, idempotent=true, destructive=false, and openWorld=true. The description adds important context beyond that: flatten makes the result non-editable, unknown field names error with suggestions, and the operation uses one render. It still omits details like whether flatten is irreversible or what gets returned.

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 with the core action front-loaded and no wasted words. The error and render-cost notes earn their place as operational context.

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

Completeness4/5

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

Given a fully described 4-parameter schema and useful annotations, the description supplies enough behavioral context for correct invocation: field typing, strict/unknown-name behavior, flattening, and a render hint. Minor gaps remain around output and flatten irreversibility, but the essentials are covered.

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 schema already documents all four parameters, including the field value types and strict/flatten semantics. The description reinforces checkbox formatting as true/false and field-name-based behavior, but adds only marginal meaning beyond the schema.

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 ('Fill a PDF form's fields by name') and enumerates the supported field types, so an agent knows exactly what the tool does. It does not explicitly differentiate from siblings such as list_pdf_form_fields, which is the one gap keeping it from 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?

It gives useful behavioral context ('Unknown field names are an error with suggestions', optional flatten) but does not state when to reach for this tool versus list_pdf_form_fields to discover field names first. Usage is implied rather than explicitly routed.

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

All PDFOven toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources