FreeDailyPro PDF Tools

pdf_flatten

Read-onlyIdempotent

Permanently flatten a PDF's fillable form fields

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_flatten"
  }
}

Input Schema

Name	Required	Description	Default
`fileBase64`	Yes	The input file as a base64 string, without a data: prefix.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 13, 2026
- removedInput schema / $schema
```
Removed value: -"http://json-schema.org/draft-07/schema#"
```
- removedInput schema / additionalProperties
```
Removed value: -false
```
- addedInput schema / properties / fileBase64 / description
```
Added value: +"The input file as a base64 string, without a data: prefix."
```
First observedOct 24, 2026

TDQS

B3.3/5.0

Behavior3/5

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

No output schema exists, and the description never says that the result is a new PDF returned as base64 with the original file untouched — the single most important behavioral fact for a file-transform tool. It does add one genuine piece of context the annotations omit: the change is permanent and specifically targets fillable form fields. Note the tension with destructiveHint=false, though readOnlyHint=true is defensible for a stateless transform that returns a new blob rather than modifying stored state.

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?

One short sentence that front-loads the irreversible modifier and the exact target of the operation. Nothing is redundant or padded.

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?

The safety profile comes from annotations and the parameter from the schema, so the definition is minimally callable. But with no output schema and no statement of what comes back, an agent cannot tell what it receives or what to do with the original document, which is a meaningful gap for a transform tool.

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?

A single parameter with 100% schema description coverage, so the schema already explains fileBase64 and its no-prefix requirement. The description adds no file-type constraints, size limits, or encoding notes beyond that, matching the baseline for a fully documented single parameter.

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 a specific verb and resource ('flatten a PDF's fillable form fields') plus the effect ('Permanently'), which is enough to separate it from pdf_fill_form and pdf_parse_fillable_form without opening a schema. It stops short of explicitly naming the nearest sibling (pdf_fill_form), so an agent must infer the fill-vs-flatten distinction from domain knowledge.

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 when-to-use guidance, no prerequisites (e.g., that the PDF must actually contain fillable fields), and no stated alternative such as pdf_fill_form for agents that want to populate rather than lock fields. Usage is only implied by the verb in the name.

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?