Skip to main content
Glama

pdf_read_form

Extract AcroForm fields and their values from a PDF, then save them as JSON or return them as an object for form processing.

Instructions

Extract AcroForm fields and values from a PDF. [Input: PDF (.pdf) | Output: JSON file (.json) or object]

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>"
    },
    "name": "pdf_read_form"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYesThe input PDF file path.
outputNoThe optional output JSON file path.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does disclose the important part: output goes to a JSON file when a path is supplied, otherwise an object is returned. It says nothing about what happens on PDFs with no AcroForm fields, encrypted/password-protected inputs, or how field names and hierarchy are represented.

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 compact sentences, purpose front-loaded, with the input/output contract in a bracketed shorthand that adds information without padding. Nothing is redundant.

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

Completeness3/5

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

For a simple two-parameter read tool this is nearly sufficient, but with no annotations and no output schema, the description is the only place the return shape could be described, and it says only 'JSON file or object' without any hint of the field/value structure. Edge-case behavior is also unaddressed.

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

Parameters4/5

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

Schema coverage is 100%, so a baseline of 3 is warranted, and the description goes slightly beyond it by clarifying that the optional output path yields a JSON file while its absence yields an object — a distinction the schema's 'optional output JSON file path' leaves open.

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 uses a specific verb ('Extract') and a specific resource ('AcroForm fields and values from a PDF'), which cleanly separates it from sibling mutators like pdf_create_form_field and pdf_fill_form without naming them. It stops short of an explicit 'this is read-only' statement, but the verb makes the direction unambiguous.

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?

Usage is only implied: an agent can infer you call this to read existing form fields rather than to create or fill them. There is no explicit when-to-use, when-not-to-use, or pointer to the sibling tools that write form data.

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