Skip to main content
Glama
Sign In
docrenders-mcp

docrenders-mcp

by JWhist
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

render_template_preview

Generate a preview PDF from a template using its built-in fields. Returns a signed download URL with caching for instant repeated access.

Instructions

Generate a preview PDF for a DocRenders template using its built-in preview_fields data. Returns a signed download URL. Previews are cached — repeated calls for the same template return instantly. Does not count against your render quota.

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": {
      "template": "<template>"
    },
    "name": "render_template_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
templateYesTemplate name (e.g. "invoice", "resume") or user template ID (tpl_…)
dataNoOptional data overrides. Omit to use the template's built-in preview_fields.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description discloses caching behavior, signed URL return, and quota exemption, which are beyond the schema. It could add error handling or URL expiry details.

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?

Three sentences, purpose-first, no fluff. Every sentence adds value (purpose, output, caching/quota).

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?

Covers purpose, output, caching, quota. Lacks error scenarios and authentication context, but sufficient for a simple preview tool with good sibling context.

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?

Schema coverage is 100% with descriptions for both parameters. The description repeats the concept of built-in preview_fields but adds no new semantic information beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb (Generate) and resource (preview PDF for a DocRenders template), and distinguishes from siblings like render and render_template by noting it does not count against quota and uses preview_fields.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies use for previews via caching and quota statements, but does not explicitly contrast with siblings like render_template or state when not to use.

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

Deploy Server

Other Tools