Skip to main content
Glama

DocuQueue MCP

by io.github.dvcoolarun
OverviewDiscussionsAdmin

fill_template

Create a document. Preview first, then confirm to generate PDF.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesTemplate variables as key-value pairs
marginNoPage margin (e.g., '1in', '20mm')
confirmNoSet true to generate PDF (preview runs first if false)
page_sizeNoPaper size
orientationNoPage orientation
template_idYesTemplate ID to fill

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
job_idYes
statusYes
messageNo
download_urlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • addedInput schema / properties / confirm / description
      Added value: +"Set true to generate PDF (preview runs first if false)"
    • addedInput schema / properties / data / description
      Added value: +"Template variables as key-value pairs"
    • addedInput schema / properties / margin / description
      Added value: +"Page margin (e.g., '1in', '20mm')"
    • addedInput schema / properties / orientation / description
      Added value: +"Page orientation"
    • addedInput schema / properties / page_size / description
      Added value: +"Paper size"
    • addedInput schema / properties / page_size / enum
      Added value: +[
+  "A4",
+  "Letter",
+  "Legal"
+]
    • addedInput schema / properties / template_id / description
      Added value: +"Template ID to fill"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "download_url": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "job_id": {
+      "type": "string"
+    },
+    "message": {
+      "type": "string"
+    },
+    "status": {
+      "enum": [
+        "pending",
+        "processing",
+        "completed",
+        "failed"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "job_id",
+    "status"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

It adds the non-obvious preview-then-confirm behavior, which is useful beyond the annotations. But it is ambiguous about the confirm=true path (schema says preview runs first if false, implying confirm=true may skip preview), and it does not mention side effects, state changes, or what preview returns.

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?

Two short sentences with no filler; the core behavior is stated up front. Every word contributes to the agent's understanding.

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?

With 6 parametershol and a nested data object, the description is quite sparseould do more to clarify the two-step call sequence and the role of confirm, especially given schema's hint that preview only runs when confirm is false. The output schema and parameter schemas cover return values and fields, so the remaining gap is behavioral flow.

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%, so the baseline is 3. The description adds minimal parameter meaning beyond confirming the preview/confirm flow, which the schema already documents on the confirm 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?

The description states a specific verb and resource: 'Create a document' via template filling, with the distinctive two-step behavior 'Preview first, then confirm to generate PDF.' It is clear enough to separate from preview_template and create_template, though it does not explicitly say 'fill a template with data' or name sibling contrasts.

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

Usage Guidelines3/5

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

The description gives an implied workflow: preview first, then confirm to produce the PDF. However, it does not state when to prefer this tool over preview_template or create_template, nor does it explain when confirmation is required or can be skipped.

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

All DocuQueue MCP toolsInspect
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