FreeSign — Free e-signature

Create signing envelope

create_signing_envelope

Create a FreeSign envelope from a PDF SHA-256 hash. Do not send PDF bytes. The created envelope is NOT yet session-bound — the browser that opens the returned signing_url generates an ECDSA P-256 keypair locally and POSTs the public JWK to /api/envelopes/{id}/session-bind before any protected request will succeed. AI agents calling this tool just hand the signing_url to a human, who continues in a browser.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`document_sha256`	Yes	SHA-256 of the original PDF bytes, computed locally by the user or agent.

Output Schema

TableJSON Schema

Name	Required	Description
`expires_at`	Yes
`envelope_id`	Yes
`signing_url`	Yes
`session_binding_required`	No	True when the envelope still needs the browser to call /api/envelopes/{id}/session-bind. Always true for MCP-created envelopes.

TDQS

A4.7/5.0

Behavior5/5

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

No annotations provided, so description carries full burden. It explains that the envelope is not session-bound, the browser generates an ECDSA P-256 keypair, and that the human continues in a browser. This fully discloses the behavioral traits.

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?

Three sentences, front-loaded with purpose, concise instructions, and no unnecessary details. Every sentence adds value.

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?

With one parameter, schema covering it, and an output schema present, the description covers the entire workflow and safety considerations, making it complete.

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% and the parameter is well-described in schema. The description adds value by specifying that the hash is used to reference the PDF and instructs not to send PDF bytes, which is beyond schema.

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 tool creates a FreeSign envelope from a PDF SHA-256 hash, distinguishing it from sibling tools that are for verification/audit purposes.

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?

Provides explicit guidance: 'Do not send PDF bytes' and explains the session-binding flow, including that the AI agent hands the signing_url to a human. While it doesn't mention alternatives, the siblings are clearly different.

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

All FreeSign — Free e-signature tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0

Disambiguation5/5

Each tool targets a distinct function: envelope creation, OTS proof retrieval, receipt retrieval, audit chain verification, and document hash lookup. No overlap in purposes.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (create_signing_envelope, get_ots_proof, etc.) with imperative verbs and clear noun phrases.

Tool Count5/5

With 5 tools, the server is well-scoped for a free e-signature service focusing on creation and verification, covering the core workflow without unnecessary extras.

Completeness4/5

The tool set covers the primary use cases: creating envelopes and retrieving/verifying evidence. Minor gaps like envelope listing or status checks are absent, but not critical for the stated purpose.

Resources

Need Help?