structuredContent). Errors come back as tool errors with a readable
message, for example Blocked by policy: ... or Sendforsign API error (404): .... Each tool calls the public
REST API, so the same permissions apply.
“Needs mode” is the lowest agent mode that allows the tool:
read_only <
draft < send. Tools are annotated for MCP clients: read tools carry readOnlyHint, archive_contract carries
destructiveHint, and send_for_signature carries openWorldHint (it reaches people outside the conversation), so
clients that ask before risky calls can do so.
Most tools accept an optional userKey argument that selects the tenant for that call; without it, the
X-Sendforsign-User-Key header or the account’s default user is used. On an OAuth connection where a user was picked
on the consent screen, that user is a limit: a different userKey is refused with
Blocked by policy: this connection is limited to userKey …, and list_users / create_user are blocked.
Field roles (filledBy)
Tools describe template and contract fields with a filledBy value that maps to the REST
fillingType:
The agent should fill only
owner fields and leave recipient fields to the recipients.
get_connection_info
Shows how this connection is configured. Call it first if unsure what you are allowed to do. Arguments: none. Returns:mode, clientKey, userKey, agent, onBehalfOf, allowedRecipientDomains ("any" or a list),
auditLog ("on"/"off"), auth ("oauth" or "header"), userKeyIsLimit (true when an OAuth grant is
restricted to one user), sendingRequiresConfirm: true.
list_templates
Lists templates available to the account or tenant. Use a template whenever the user asks for a standard document (NDA, service agreement, offer) before drafting from scratch. Arguments:userKey?
Returns: templates[] with templateKey, name, changeTime.
get_template
A template and its fields, including who fills each. Arguments:templateKey, includeContent? (default false; true adds the HTML body), userKey?
Returns: templateKey, name, placeholders[] (placeholderKey, name, value, filledBy, recipientKey),
content?.
list_contracts
Lists contracts with their status. Arguments:status? (e.g. Created, Sent, Seen, Signed, Fully signed, Archived; case-insensitive),
nameContains?, limit? (1–500, default 50), userKey?
Returns: total, contracts[] with contractKey, name, status, createTime, changeTime.
get_contract
Arguments:contractKey, includeContent? (default false), userKey?
Returns: contractKey, name, status, templateKey (the template it was created from, or null),
createTime, changeTime, recipients[] (with signingUrl), placeholders[], content?.
create_contract
Creates a draft contract. It never emails anyone, even when you pass recipients. Arguments:
Pass
templateKey or content.
Returns: contractKey, status: "draft", recipients[] with signingUrl, filled[] (per field: field,
ok, error?) when fields were given, unfilledFields[] (owner and fixed fields still empty),
fieldsForRecipients[], and next — a hint for the next step.
update_contract
Renames a draft and/or replaces its body. Only for contracts that have not been sent. Arguments:contractKey, name?, content?, contentFormat? (default markdown), userKey?
Returns: contractKey, updated[] (the fields changed).
list_placeholders
Arguments:contractKey? or templateKey? (one is required)
Returns: placeholders[] with placeholderKey, name, value, filledBy, recipientKey.
fill_placeholders
Sets field values in a contract, byplaceholderKey or by name (case-insensitive), and can change who fills a field.
Arguments: contractKey, fields[] of { placeholderKey?, name?, value?, filledBy?, recipientKey? }.
recipientKey is required when filledBy is specific_recipient. Changing filledBy to anything else clears the
assigned recipient.
Returns: contractKey, results[] with field, placeholderKey, ok, error? per field. One failed field
does not stop the others.
add_recipients
Adds signers, approvers or viewers without emailing them. Signing order continues after existing recipients unless you passposition.
Arguments: contractKey, recipients[] (as in create_contract, at least one), userKey?
Returns: contractKey, recipients[] (all recipients of the contract) with recipientKey and signingUrl.
The signingUrl (https://app.sendforsign.com/sharing/{recipientKey}) can be shown in your own product instead of
sending email. See embedded signing.
list_recipients
Arguments:contractKey
Returns: contractKey, recipients[] with recipientKey, fullname, email, action, position,
customMessage, signingUrl.
send_for_signature
Emails signing invitations. This contacts real people. Before calling, the agent must show the user the contract name, the recipients and their roles, get explicit approval, and then passconfirm: true. Without it the tool returns Not executed: ... needs confirm: true and sends
nothing. Allowed only in send mode; recipients are checked against the domain allowlist.
Arguments: contractKey, confirm (boolean, must be true), recipientKeys? (send only to these; default: all
recipients), customMessage? (overrides the invitation message), userKey?
Returns: contractKey, sentTo[] with email, action, signingUrl.
get_contract_timeline
Event history of a contract, plus the agent actions recorded for it when the audit log is on. Arguments:contractKey
Returns: contractKey, events[] (time, status, name, email), agentActions[]? (create_time, agent,
on_behalf_of, mode, tool, outcome, message, hash).
download_contract_pdf
Arguments:contractKey
Returns: contractKey, mimeType: "application/pdf", bytes, base64.
archive_contract
Archives a contract: it leaves active lists and can no longer be signed. Needsconfirm: true after explicit user
approval, and send mode.
Arguments: contractKey, confirm, userKey?
Returns: contractKey, archived: true.
list_users
For products that embed Sendforsign: lists tenants (users) of the client. Each has its own templates and contracts, addressed byuserKey.
Arguments: none.
Returns: users[] with userKey, fullname, email, customKey.
create_user
Creates a tenant and returns itsuserKey. customKey is your own ID for it, so you can map back.
Arguments: fullname, email, customKey?
Returns: userKey, fullname, email, customKey.