put_v1_legal_templates_id

SaveLegalTemplateOverride saves the org's own version of a template — a custom NDA, a house MSA — and returns it with its new version number.

SaveLegalTemplateOverride saves the org's own version of a template — a custom NDA, a house MSA — and returns it with its new version number. It takes effect for that org only; other orgs keep the built-in.

Two boundaries cannot be crossed here. Overriding a built-in INHERITS its category and its counsel-review posture, which can be raised but never dropped; and a formation or equity template is counsel-review whatever the caller sends, so no org can generate a securities-class document without the notice.

The body is validated on save, not at generation: a template that references an UNDECLARED merge field is refused with 400 rather than stored and rendered blank into a contract months later.


Tool	`put_v1_legal_templates_id`
Door	`https://api.hanzo.ai/v1/mcp`
Method	`tools/call` (JSON-RPC 2.0)
Arguments	6
Operation	`PUT /v1/legal/templates/{id}`
Product	legal

Arguments

Field	Type	Required	Default	Values	Description
`body`	`string`	—	—	—	Body is the text/template source. Required. Every {{.key}} it references must be declared in Fields, or the save is refused rather than rendering a blank into a contract later.
`category`	`string`	—	—	—	Category groups the template: formation, equity, ops or sales. Optional when overriding a built-in, which supplies its own.
`counselReview`	`boolean`	—	—	—	CounselReview marks a template whose documents must carry the counsel notice. It can be raised but never lowered: a formation or equity template is always counsel-review, and an override of a counsel-review built-in stays one.
`fields`	`Field[]`	—	—	—	Fields declares the merge fields the body consumes. Every declared field is REQUIRED at generation — the engine fails closed on a missing one.
`id`	`string`	—	—	—	ID is the template to override, from the path. Overriding a built-in id inherits that built-in's category, title and counsel-review posture.
`title`	`string`	—	—	—	Title is the template's display name. Required unless a built-in supplies it.

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

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

Field

Field	Type	Required	Default	Values	Description
`key`	`string`	—	—	—	—
`label`	`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": "put_v1_legal_templates_id",
         "arguments": {
           "body": "<body>",
           "category": "<category>",
           "counselReview": false,
           "fields": [
             {
               "key": "<key>",
               "label": "<label>"
             }
           ],
           "id": "<id>",
           "title": "<title>"
         }
       }
     }'

Values are the operation's own defaults and enumerated values where it declares them, and a <placeholder> where neither source declares one. counselReview holds a stand-in that cannot be spelled that way — JSON gives a number, a boolean and a timestamp no placeholder form — so that value is this page's, not the API's. Neither the door nor the operation 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
`put_v1_legal_templates_id`	`PUT /v1/legal/templates/{id}`	legal	Saves the org's own version of a template — a custom NDA, a house MSA — and returns it…

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).