FreeDailyPro PDF Tools

pdf_parse_fillable_form

Read-onlyIdempotent

Parse a PDF's fillable form fields — lists every fillable field's name, type (text, checkbox, dropdown, radio, optionlist), current value and options so you know what to fill

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": {
      "fileBase64": "<fileBase64>"
    },
    "name": "pdf_parse_fillable_form"
  }
}

Input Schema

Name	Required	Description	Default
`fileBase64`	Yes	The PDF file, base64-encoded

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 13, 2026
- removedInput schema / $schema
```
Removed value: -"http://json-schema.org/draft-07/schema#"
```
- removedInput schema / additionalProperties
```
Removed value: -false
```
First observedOct 24, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful context by spelling out the shape of each returned field (name, type, value, options) despite there being no output schema, but it is silent on edge behavior such as PDFs with no form fields or malformed input.

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?

One sentence, front-loaded with the action and resource, with the return contents immediately following. Every clause earns its place; only the closing rationale ('so you know what to fill') is mild filler rather than new information.

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?

For a one-parameter read-only inspection tool, the description covers purpose, return contents, and intended follow-up action, and annotations cover safety. The only gap is undefined behavior for non-fillable or invalid PDFs, which matters since no output schema exists to explain results.

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?

There is a single parameter (fileBase64) whose schema description already states 'The PDF file, base64-encoded' at 100% coverage. The description adds no encoding format, size limits, or constraint details beyond the schema, so the baseline of 3 applies.

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?

Uses a specific verb ('Parse') on a specific resource ('a PDF's fillable form fields') and enumerates what is returned (name, type, current value, options). This distinguishes it from the write-side sibling pdf_fill_form implicitly through the stated goal, though it never names that sibling.

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 trailing clause 'so you know what to fill' implies the intended workflow (inspect fields, then fill them), which is useful context. However, there is no explicit when-to-use/when-not statement, no mention of what happens with non-fillable PDFs, and no named alternative.

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

All FreeDailyPro PDF Tools tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?