zsign

Download Signed Document

download_signed_document

Read-onlyIdempotent

Download the sealed, signed PDF. Takes the completed_document_id from get_envelope_status; the original document_id also works and resolves to that document's most recent completed session. Returns the bytes as content_base64 with content_type from the HTTP response. PDF responses also include pdf_base64 (same bytes). Requires Authorization: Bearer zs_....

document_id: one of `documents[].id` from get_envelope_status to download
just that document (its pages plus the certificate pages — an extract;
the certificate hash identifies the full envelope). `format='zip'`:
every document as its own PDF in one archive (`application/zip`).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`format`	No
`document_id`	No
`completed_document_id`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 12, 2026

addedInput schema / properties / document_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Document Id"
+}

addedInput schema / properties / format

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Format"
+}

First observedJul 21, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the readOnlyHint and idempotentHint annotations, the description reveals the required Authorization header format, the response fields content_base64 and content_type, the pdf_base64 alias for PDF responses, the zip behavior, and the resolution of document_id to the most recent completed session. This is substantial behavioral context that annotations alone do not provide.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is more than a sound bite and repeats document_id-related guidance in two places, but each sentence adds a useful detail: auth, output encoding, certificate pages, and zip behavior. The core download purpose is front-loaded and the extra length is mostly justified by the tool's parameter complexity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given three parameters, zero schema descriptions, and a sibling download_certificate tool, the description covers the key facts an agent needs: ID sources, optional document selection, output format, authentication, and return field names. Nothing essential to invoking the tool correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the burden of explaining parameters. It explains completed_document_id as the identifier from get_envelope_status, document_id as a way to download an individual document extract, and format='zip' as the archive behavior. However, the precise interaction between completed_document_id and document_id, and the accepted values for format beyond zip, are not fully spelled out.

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 opens with a specific action and resource: 'Download the sealed, signed PDF.' It clearly positions this as the tool for retrieving signed documents and even distinguishes it from the sibling download_certificate by explaining that document PDFs include certificate pages and a certificate hash for the full envelope.

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 gives clear context by telling the agent to obtain completed_document_id from get_envelope_status and notes that document_id can also be used to download a specific document. It does not explicitly name alternatives or state when not to use this tool, but the conditions are largely inferable from the source it names.

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

All zsign tools Inspect

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

Need Help?