Skip to main content
Glama

pdf-suite

pdf_forms_inspect_and_fill

Inspect all interactive AcroForm fields in a PDF, optionally fill text/checkbox fields from JSON, and flatten form widgets.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "pdf_forms_inspect_and_fill"
  }
}

Input Schema

NameRequiredDescriptionDefault
flattenNo
inputPathNo
base64DataNo
outputPathNo
fieldValuesNoMap of fieldName -> string value 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?

No annotations are supplied, so the description carries the full behavioral burden. It does not disclose that flattening is irreversible and destroys interactive widgets, nor does it explain how the source is chosen between file path and base64 data, or what the caller must supply to persist results.

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 tight sentence with the primary action (inspect) front-loaded and the optional mutations trailing. No filler, though the three clauses could be broken out for readability given the tool's multiple modes.

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?

With five parameters, no annotations, no output schema, and thin schema coverage, the description should explain the inspection result and the input/output contract. It omits what inspection returns and how outputPath must be set to write results, leaving significant gaps for a multi-mode tool.

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

Parameters2/5

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

Schema description coverage is only 20%, with just fieldValues documented, so the description should compensate. It adds the notion of 'text/checkbox fields from JSON' but leaves inputPath, base64Data, outputPath, and flatten's effect unexplained, including how the two input sources interact.

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?

States specific verbs (inspect, fill, flatten) and a specific resource (interactive AcroForm fields in a PDF). An agent can tell this handles form fields rather than generic PDF manipulation, though it does not explicitly distinguish itself from the sibling PDF tools.

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?

The word 'optionally' signals that fill and flatten are secondary to inspection, which implies a read-only mode versus a mutating mode. However, it never states prerequisites, when to choose this over other PDF tools, or when flattening is appropriate.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources