Skip to main content
Glama

Create (and optionally send) an envelope

create_envelope

Create a Docuflex envelope. documents: inline base64 PDFs or staged uploadIds. recipients: name, email, routingOrder (1 = first), optional type (signer default, cc, certified_delivery, in_person_signer...). tabs: type (signature, initial, date_signed, text, checkbox...), page (1-based), x/y/width/height as fractions of the page from the top-left, documentIndex and recipientIndex into this request's arrays. status 'sent' sends now; omit for a draft.

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": {
      "subject": "<subject>",
      "documents": "<documents>",
      "recipients": "<recipients>"
    },
    "name": "create_envelope"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabsNo
statusNo
api_keyNoDocuflex API key (dfx_live_...). Optional if sent as the x-docuflex-api-key header.
messageNo
subjectYes
metadataNo
documentsYes
account_idNoDocuflex account id. Optional if sent as x-docuflex-account or if the key belongs to exactly one account.
recipientsYes
routingTypeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose meaningful behavior: documents may be inline base64 or staged uploadIds, recipient routingOrder 1 = first, and status controls draft versus immediate send. It omits what a draft's lifecycle looks like, permission/account requirements, error behavior, and the hard caps (20 documents, 50 recipients, 500 tabs) that a caller would want to know before a failed attempt.

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?

Front-loaded with a one-line purpose, then a compact field-by-field breakdown with no filler sentences. It reads as a dense semicolon-separated block, which is efficient but slightly harder to scan than grouped clauses would be.

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?

This is a 10-parameter nested mutation tool with no annotations and no output schema, which raises the bar considerably. The description covers the structurally complex arrays well but says nothing about what a successful call returns (presumably an envelope id needed for send/get/void), nor about the scalar parameters routingType, metadata, subject, and message.

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 only 20% across 10 parameters, and the description compensates well for the highest-risk ones: it explains the two mutually exclusive document input modes, the recipient type enumeration with signer as default, tab type values, 1-based page, x/y/width/height as page fractions from the top-left, and that documentIndex/recipientIndex index into this request's arrays. It leaves subject, message, metadata, routingType, api_key, account_id, and clientUserId unaddressed, so coverage is strong but incomplete.

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 opens with a specific verb+resource, "Create a Docuflex envelope," and the title adds that sending is optional. It is clearly distinguishable from read-side siblings like get_envelope or list_envelopes, though it does not resolve the overlap with the send_envelope sibling when status='sent'.

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?

Usage is implied through "status 'sent' sends now; omit for a draft," which tells the agent how to get either outcome. It never names send_envelope, void_envelope, or any other sibling, nor does it state prerequisites (e.g. verified account, staged upload required before referencing uploadId).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources