fill_pdf_formFill a PDF's form fields from a map of field -> value; optionally flatten. Returns a file_id and a ~1h URL.
| Name | Required | Description | Default |
|---|---|---|---|
| Yes | A file_id from a prior tool result, or a base64-encoded PDF. | ||
| fields | Yes | Map of field name to value. | |
| flatten | No | Flatten the form after filling (default false). |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the burden. It mentions the optional flatten behavior and the return of a file_id/URL, but does not disclose potential side effects, how it handles missing fields, or whether it preserves the original file. This is adequate but not comprehensive.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is one concise sentence that front-loads the main verb and resource, followed by key options and return values. No unnecessary words or repetition.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description covers the essential inputs, the optional flattening, and the return type (file_id and URL). It lacks detail on error cases or edge scenarios, but given the simplicity of the tool and absence of an output schema, it is reasonably complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema provides 100% coverage of all parameters (pdf, fields, flatten) with descriptions. The tool description itself does not add extra detail beyond what is already in the schema, so it meets the baseline for high schema coverage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose: filling a PDF's form fields with a map of field-value pairs, with an optional flatten option, and it returns a file_id and URL. This is unambiguous and differs from sibling tools such as read_pdf_form.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description does not explicitly state when to use this tool versus alternatives (e.g., read_pdf_form). It implies usage through its purpose but lacks explicit guidance or contrast with sibling tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools have clearly distinct purposes, such as extracting PDF text versus filling forms or rendering URLs to PDF versus screenshots. The only mild overlap is read_url and scrape_page, both fetching a URL, but their outputs are explicitly differentiated as clean Markdown versus raw HTML with metadata.
Names mostly follow a verb_noun pattern like extract_pdf_text, fill_pdf_form, and rotate_pdf. A few conversion tools use 'to' constructions (images_to_pdf, markdown_to_pdf, url_to_pdf) and some pluralize objects (merge_pdfs, select_pages), creating minor inconsistency but no real confusion.
With 15 tools, the set is at the upper edge of the ideal range and every tool serves a distinct, useful function within the PDF and URL processing domain. The count feels justified rather than excessive.
The PDF tooling covers creation from images and Markdown, text extraction, form filling and reading, merging, splitting, rotating, selecting pages, and watermarking. URL handling covers reading as Markdown, scraping raw HTML/metadata, generating PDFs, and taking screenshots, providing well-rounded coverage for the stated domain.