post_v1_legal_documents_id_sign

RequestLegalSignature opens an e-signature request over one document and moves it to out_for_signature, returning the provider's reference for the request.

The provider is whatever this deployment has wired. The honest default is "manual": the request is recorded and the org fulfils it out of band — nothing here fabricates a signature, and the stub never reports itself complete.


Tool	`post_v1_legal_documents_id_sign`
Door	`https://api.hanzo.ai/v1/mcp`
Method	`tools/call` (JSON-RPC 2.0)
Arguments	2
Operation	`POST /v1/legal/documents/{id}/sign`
Product	legal

Arguments

Field	Type	Required	Default	Values	Description
`id`	`string`	—	—	—	ID is the document to send for signature, from the path.
`signers`	`legalSigner[]`	—	—	—	Signers are the people who must sign, by name and email. At least one is required.

tools/list declares a type and a description for each field and nothing further. A — means neither the door nor that operation constrains the field.

Object types

legalSigner is an object this tool's fields are made of, declared inside the tool's own schema and enumerated in full below.

legalSigner

Field	Type	Required	Default	Values	Description
`email`	`string`	—	—	—	—
`name`	`string`	—	—	—	—

Call it

A tools/call carries every argument in one flat object — nothing binds to a path or a query string. Nothing above is required, so every declared argument is shown rather than a guess at which matter.

curl -X POST https://api.hanzo.ai/v1/mcp \
  -H "Authorization: Bearer $HANZO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
       "jsonrpc": "2.0",
       "id": 1,
       "method": "tools/call",
       "params": {
         "name": "post_v1_legal_documents_id_sign",
         "arguments": {
           "id": "<id>",
           "signers": [
             {
               "email": "<email>",
               "name": "<name>"
             }
           ]
         }
       }
     }'

Values are the operation's own defaults and enumerated values where it declares them, and a <placeholder> where neither source declares one. tools/list needs no credential; tools/call does — called without one the door answers HTTP 200 with a JSON-RPC result whose isError is set and whose text says what was missing. How to get a key →

The operation behind it

Operation	Route	Product	Summary
`post_v1_legal_documents_id_sign`	`POST /v1/legal/documents/{id}/sign`	legal	Opens an e-signature request over one document and moves it to out_for_signature,…

The same capability over plain HTTP is in the legal API reference, on https://api.hanzo.ai.

All 755 tools · The door · API reference

Generated from tools/list on https://api.hanzo.ai/v1/mcp — 833 tools captured 2026-08-01, of which 755 are documented here (the operator surface is not published) (this build read the vendored copy; the door was unreachable).