Skip to main content
Glama
Sign In
mcp-Docuplete

mcp-Docuplete

Official
by Docuplete
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

generate-pdf

Finalize a session and trigger PDF generation, returning a download URL for the completed document packet.

Instructions

Finalise a session and trigger PDF generation. Returns a download URL for the completed PDF packet. Call this once the session status is 'in_progress' or after filling answers programmatically.

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": {
      "token": "<token>"
    },
    "name": "generate-pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYesThe session token to generate the PDF for.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the burden of disclosure. It mentions that the tool finalises the session and returns a download URL, which is useful, but it doesn't disclose whether the operation is reversible or any side effects beyond finalisation. Thus, moderate transparency.

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?

The description is two sentences, front-loaded with the primary purpose, and each sentence adds value without waste.

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?

For a simple one-parameter tool with no output schema, the description covers the trigger condition, the action, and the return value, which is adequate for an agent to invoke correctly. It doesn't elaborate on error cases, but they are not essential given the tool's simplicity.

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 a clear description for the one parameter 'token'. The description adds no further parameter details, so baseline 3 applies.

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 tool's function with a specific verb ('trigger PDF generation') and resource ('a session'), and it distinguishes itself from sibling tools which are all listing/getting/creating sessions or packages.

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?

It provides explicit usage guidance with the condition 'once the session status is in_progress or after filling answers programmatically', which tells the agent when to invoke it. No alternative tool is mentioned, but siblings are clearly different, so there's no exclusion needed.

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