Skip to main content
Glama
signnow

SignNow MCP Server

Official
by signnow
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

Upload document

upload_document

Upload a document into SignNow for e-signing. Accepts file path, URL, or resource. Supports PDF, DOCX, and images up to 40 MB. On success, choose to prepare an invite, send for signing, or self-sign.

Instructions

Upload a document to SignNow from a local file path, public URL, or MCP resource attachment. Supported file types: PDF, DOC, DOCX, PNG, JPG, JPEG. Max file size: 40 MB. On success the response includes a 'next_steps' array (prepare invite / send for signing / self-sign) and an 'agent_guidance' string — present those options to the user and wait for them to choose before calling any follow-up tool. NOTE: For URL uploads, the returned filename is locally inferred and may differ from how SignNow names the document.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
resource_uriNoMCP resource URI of an attached file (preferred when your client supports resource attachments). Provide exactly one of resource_uri, file_path, or file_url.
file_pathNoAbsolute or ~-relative path to a local file to upload. The resolved path must be within the safe upload base directory (SAFE_UPLOAD_BASE, defaulting to your home directory); paths outside that base (e.g. /tmp/foo.pdf) will be rejected. Supported: .pdf, .doc, .docx, .png, .jpg, .jpeg. Provide exactly one of resource_uri, file_path, or file_url.
file_urlNoPublicly accessible URL to the file to upload. SignNow will fetch the file from this URL. Provide exactly one of resource_uri, file_path, or file_url.
filenameNoOptional custom name for the document as it will appear in SignNow. If omitted, the name is derived from the file path, URL, or resource URI. Required when using resource_uri and the filename cannot be inferred.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
document_idYesID of the uploaded document in SignNow
filenameYesName of the uploaded file. For 'local_file' and 'resource' sources this matches the name sent to SignNow. For 'url' source this is locally inferred from the URL and may differ from how SignNow actually names the document.
sourceYesHow the file was provided: 'local_file' (read from local path), 'url' (fetched by SignNow from URL), 'resource' (attached via MCP resource protocol)
next_stepsYesSuggested follow-up actions the agent MUST present to the user after a successful upload, in the given order. Ask the user which one they want before proceeding — do not silently pick one.
agent_guidanceYesInstruction for the agent: after upload, present the next_steps options to the user and wait for them to choose before calling any follow-up tool. Load the 'signnow101' skill via signnow_skills(skill_name='signnow101') if more context is needed.

Tool Definition Quality

A4.7/5.0
Behavior5/5

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

Beyond annotations (which only set openWorldHint=true), the description adds critical behavioral details: max file size (40 MB), supported file types, safe upload base directory restriction, URL filename inference note, and the response structure (next_steps, agent_guidance). No contradiction 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?

Two well-structured paragraphs with no wasted words. Each sentence serves a purpose: purpose, constraints, supported types/size, response handling, and a caveat.

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 the schema coverage and existence of output schema, the description covers all necessary aspects: input constraints, behavioral traits, post-upload workflow. No gaps for an upload tool.

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 coverage is 100%, but the description adds cross-parameter clarity (exactly one of three) and a special condition (filename required when using resource_uri if not inferrable). This goes beyond schema descriptions.

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 the verb ('Upload') and resource ('document to SignNow') and lists the three input sources (local file, URL, MCP attachment). It distinguishes from sibling tools which are about invites, templates, and other operations.

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 explicitly says to provide exactly one of the three input methods and provides post-upload guidance (present next_steps options to user). It lacks explicit when-not-to-use scenarios, but sibling tools cover different operations.

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/signnow/sn-mcp-server'

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