formfeed
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FORMFEED_REGION | No | API region of the workspace. | eu |
| FORMFEED_API_KEY | Yes | Formfeed API key from the app (API keys). ff_test_… renders free with a watermark, ff_live_… consumes units. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_templatesB | Templates of the workspace the API key belongs to, with slug, kind (pdf, image, docx for Word, pptx for PowerPoint), engine and published version. |
| get_template_schemaA | JSON Schema of the |
| validate_templateA | Checks a template with data without rendering; free. With a template slug the API checks the version a render uses (the published one, else the latest) as the render would: syntax, header and footer, errors that happen only with this data, and the data against the template's stored JSON Schema (a wrong type or a missing required field is an error). With html plus engine it compiles offline and reports syntax errors, unknown filters and variables missing from the data. Warnings leave ok true: treat each one as a question to settle before rendering. For Word and PowerPoint templates the findings name the document part and paragraph. |
| renderA | Renders a template (with data) or raw HTML to a PDF or image, or a Word or PowerPoint template to DOCX, PPTX or PDF, and returns a download URL. Live keys consume units; test keys render free with a watermark. |
| convert_to_pdfA | Converts a Word, Excel, PowerPoint, OpenDocument, RTF or HTML document (up to 20 MB) to a PDF and returns a download URL (Starter plan and above; units follow the PDF rule). Pass exactly one source: render_id, the render of a Word or PowerPoint template (output docx or pptx); path, a file on this machine; or file_base64 with file_name. The document is converted and not kept. |
| get_renderA | Status, download URL and error of a render by id (rnd_…). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool addresses a distinct stage in the document generation workflow: listing templates, inspecting schemas, validating, rendering, converting, and retrieving results. Even validate_template and render are clearly separated by purpose—one checks without producing output, the other produces a downloadable render.
Tool names mostly follow a clear verb_noun pattern like list_templates, get_template_schema, validate_template, and get_render. The bare verb 'render' is a minor deviation since it omits an explicit object, but the overall naming remains predictable and readable.
Six tools is a well-scoped count for a document rendering and conversion server. Each tool serves a necessary function in the workflow without redundancy or bloat.
The tool surface covers the full lifecycle: discover available templates, understand their required data schema, validate before rendering, render to multiple formats, convert outputs to PDF, and check render status or retrieve results. No obvious gaps exist for the server's stated purpose.