rendoc
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RENDOC_API_KEY | Yes | Your rendoc API key for authentication | |
| RENDOC_API_URL | No | Base URL for the rendoc API (useful for self-hosted instances) | https://rendoc.dev |
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
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_documentA | Generate a PDF document from a template and data. Returns a download URL for the generated PDF. Provide either |
| list_templatesA | List available document templates. Optionally filter by category. Returns template names, slugs, categories, descriptions, paper sizes, and IDs. Use the returned ID with |
| get_documentA | Get details about a previously generated document by its ID. Returns the document status, download URL, file size, page count, and creation date. |
| get_usageA | Get current API usage statistics for this billing month. Returns your plan name, document count vs limit, page count, and remaining quota. |
| preview_templateA | Get the full markup, styles, and data schema of a template. Use this to inspect a template before generating a document. The schema shows which data fields the template expects. Sample data (if available) shows example values for each field. |
| create_templateA | Create a new reusable document template. Templates use HTML/Handlebars markup with a JSON schema defining the expected data fields. Once created, use the returned template ID with |
| delete_templateA | Delete a template by its ID. This action is irreversible. Only templates you own can be deleted. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| templates | JSON listing of all available document templates |
TDQS
Scored across 7 tools
Each tool has a clearly distinct purpose with no overlap: create_template, delete_template, list_templates, and preview_template handle template management; generate_document and get_document handle document generation and retrieval; get_usage provides API usage stats. The descriptions reinforce these boundaries, making tool selection unambiguous.
All tools follow a consistent verb_noun pattern with snake_case naming (e.g., create_template, generate_document, get_usage). The verbs are clear and appropriate for their actions, and there are no deviations or mixed conventions throughout the set.
With 7 tools, the server is well-scoped for document generation and template management. Each tool earns its place by covering essential operations like CRUD for templates, document generation, retrieval, and usage monitoring, without being too sparse or bloated.
The tool set provides complete coverage for the document generation domain: full CRUD for templates (create, delete, list, preview), document generation and retrieval, and usage monitoring. There are no obvious gaps, and the tools support core workflows from template creation to PDF output without dead ends.