Skip to main content
Glama
signdocsbrasil

SignDocs Brasil MCP Server

Official

Create signing session

create_signing_session
Destructive

Create a single-signer express signing session for PDF documents or action authentication, returning a signing URL and session IDs.

Instructions

⚠️ This performs a consequential, possibly irreversible action (legally-binding signature request and/or quota consumption). Confirm with the human before calling. Create a single-signer "express" signing (or action-authentication) session and return its IDs plus a ready-to-share signingUrl (url + embed token). Consumes signature quota.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ownerNoThe requester (distinct from the signer). When set and signer.email differs, SignDocs auto-emails the signer an invite and notifies the owner on completion. Omit to deliver links yourself via webhooks.
actionNoWhat is being authenticated — used when purpose=ACTION_AUTHENTICATION.
localeNoUI/email language. Default pt-BR.
signerYesThe person who will sign / authenticate.
purposeYesDOCUMENT_SIGNATURE to sign a PDF; ACTION_AUTHENTICATION to authenticate an action with no document.
metadataNoFree-form key/value tags (keys ≤256, values ≤1024 chars).
cancelUrlNoRedirect URL if the signer cancels.
returnUrlNoRedirect URL after completion (sessionId appended as query param).
customStepsNoOrdered step types — REQUIRED only when policyProfile=CUSTOM (e.g. ["CLICKWRAP","OTP"]).
documentUrlNoDirect, public HTTPS link to the PDF (≤10MB) — the server fetches it. Must return raw PDF bytes (S3/Dropbox ?dl=1/public .pdf). NOTE: a Google Drive "/view" link or a private file will NOT work.
uploadTokenNoToken from request_document_upload, after the user uploaded the PDF on the drag-and-drop page. Best for local files or private Google Drive files (download then drag in). Provide one of documentBase64 / documentUrl / uploadToken.
policyProfileYesIdentity-assurance profile: CLICK_ONLY, CLICK_PLUS_OTP, BIOMETRIC, BIOMETRIC_PLUS_OTP, or CUSTOM. Read the signdocs://policy-profiles resource for the authoritative list — an invalid value returns 400.
documentBase64NoBase64-encoded PDF (≤10MB). Provide this OR documentUrl when purpose=DOCUMENT_SIGNATURE.
idempotencyKeyNoIdempotency key for safe retries; a UUID is generated if omitted.
documentFilenameNoOriginal filename, e.g. contrato.pdf.
expiresInMinutesNoSession lifetime, 5–1440 min (default 60).
Behavior5/5

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

The description adds significant behavioral context beyond annotations: it labels the action as consequential, possibly irreversible, legally-binding, and quota-consuming. This aligns with destructiveHint=true and readOnlyHint=false, and provides richer detail for the agent. No contradictions with annotations.

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 very concise: three sentences. The warning is bolded and front-loaded for immediate attention. Every sentence adds essential information without redundancy.

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?

Despite no output schema, the description states what is returned (IDs and signingUrl). It covers the high-stakes nature and quota consumption. For a complex tool with 16 parameters, the description is somewhat brief but adequately sets context. Missing details about return structure are partially compensated by schema descriptions.

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%, so the description adds limited parameter-specific meaning. It mentions 'single-signer' implying signer is a single object, and 'express' hints at speed, but overall the schema already documents parameters thoroughly. The description's value here is marginal.

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 it creates a single-signer 'express' signing session and returns IDs and a signing URL. It specifies the purpose (legally-binding signature or action authentication) and distinguishes from siblings like create_envelope by emphasizing single-signer express mode.

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?

The description includes a prominent warning about consequential actions and advises confirming with the human, which serves as a usage guideline. It also mentions quota consumption. However, it does not explicitly contrast with sibling tools like create_envelope for multi-signer cases, so some guidance is implicit rather than explicit.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/signdocsbrasil/signdocs-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server