Skip to main content
Glama

Embedded signing URL

get_signing_url

Short-lived signing URL for a current-tier recipient (embedded signing). Provide the recipient's email or clientUserId as used on the envelope and a returnUrl.

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": {
      "envelope_id": "<envelope_id>"
    },
    "name": "get_signing_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailNo
api_keyNoDocuflex API key (dfx_live_...). Optional if sent as the x-docuflex-api-key header.
userNameNo
returnUrlNo
account_idNoDocuflex account id. Optional if sent as x-docuflex-account or if the key belongs to exactly one account.
envelope_idYes
clientUserIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does disclose two real traits — the URL is 'short-lived' and only valid for a 'current-tier recipient' — which is meaningful beyond structured data, but it omits whether the URL is single-use, what error occurs if the recipient is in a later tier, and what auth scope is needed.

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 dense sentences, front-loaded with the purpose followed by the calling instruction. No filler, no restatement of the title.

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?

For a 7-parameter, no-output-schema, no-annotation tool, the definition covers the core call path but not the edges: auth via api_key/account_id (documented only in schema property text), what the return value looks like, and the constraint that exactly one of email/clientUserId identifies the signer. Adequate but with clear gaps.

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

Parameters2/5

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

Schema description coverage is only 29% across 7 parameters, so the description must compensate. It adds genuinely useful semantics for the email/clientUserId alternative ('as used on the envelope') and confirms returnUrl, but leaves api_key, account_id, userName, and envelope_id entirely unaddressed, and never states that one of email/clientUserId is effectively mandatory despite only envelope_id being schema-required.

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 resource ('signing URL') scoped by two qualifiers: 'short-lived' and 'for a current-tier recipient (embedded signing)'. That is enough to separate it from siblings like get_envelope or send_envelope, though the term 'current-tier recipient' is unexplained jargon that an agent may not resolve.

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 rather than stated: '(embedded signing)' signals the scenario, and 'Provide the recipient's email or clientUserId as used on the envelope' implies a recipient must already exist on the envelope. There is no explicit when-to-use, no when-not-to-use, and no naming of an alternative sibling for related needs.

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