Cloud MCPlegal
legal
10 MCP tools on the Hanzo cloud door that call the legal API.
The 10 tools tools/list names for legal. Each dispatches to an operation in the legal API reference.
| Tool | Route | Arguments | Description |
|---|---|---|---|
get_v1_legal_documents | GET /v1/legal/documents | 1 | ListLegalDocuments returns the org's generated documents, newest first, WITHOUT their rendered conte |
get_v1_legal_documents_id | GET /v1/legal/documents/{id} | 1 | GetLegalDocument returns one of the org's documents WITH its rendered body. |
get_v1_legal_filings | GET /v1/legal/filings | 1 | ListLegalFilings returns the org's filing records, newest first — which documents were filed where, |
get_v1_legal_health | GET /v1/legal/health | 0 | LegalHealth reports that the legal subsystem is serving and how many built-in templates its catalog |
get_v1_legal_templates | GET /v1/legal/templates | 0 | ListLegalTemplates returns the org's effective template catalog: every built-in template, with any t |
get_v1_legal_templates_id | GET /v1/legal/templates/{id} | 1 | GetLegalTemplate returns one template resolved for the caller's org — the org's own override if it h |
post_v1_legal_documents | POST /v1/legal/documents | 2 | GenerateLegalDocument renders a document from a template and the caller's own merge data, seals it i |
post_v1_legal_documents_id_sign | POST /v1/legal/documents/{id}/sign | 2 | RequestLegalSignature opens an e-signature request over one document and moves it to out_for_signatu |
post_v1_legal_filings | POST /v1/legal/filings | 2 | CreateLegalFiling records a filing of one or more of the org's documents with a state or agency, and |
put_v1_legal_templates_id | PUT /v1/legal/templates/{id} | 6 | SaveLegalTemplateOverride saves the org's own version of a template — a custom NDA, a house MSA — an |
Generated from tools/list on https://api.hanzo.ai/v1/mcp — 834 tools captured 2026-08-01 (this build read the vendored copy; the door was unreachable).
How is this guide?