put_v1_translate_memory
Review records a human decision on one translation-memory entry, and returns the entry as stored.
Review records a human decision on one translation-memory entry, and returns the entry as stored. A human write always wins over the stored value, and once it lands at approved or published no machine write can move it again — which is what makes a locale rebuild safe to run against reviewed work.
The org is ALWAYS the validated principal's org, never a request field, so a review can only ever land in the caller's own memory.
| Tool | put_v1_translate_memory |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 6 |
| Operation | PUT /v1/translate/memory |
| Product | translate |
Arguments
| Field | Type | Required | Default | Values | Description |
|---|---|---|---|---|---|
glossary | object | — | — | — | Glossary is the terminology the entry was translated under. Its VERSION — the digest of the sorted terms — is part of the entry's identity, so editing a term yields a new entry rather than overwriting the old rendering. |
source | string | — | — | — | Source is the ORIGINAL string this entry translates. Required; part of the entry's identity, so a different source is a different entry. |
state | string | — | — | — | State is the entry's new position on the review ladder: suggested, approved or published. machine is engine-only and is refused here — a human may not demote a string back into the churn. |
target | string | — | — | — | Target is the target language tag (BCP-47, e.g. "es" or "pt-BR"). Required; part of the entry's identity. |
text | string | — | — | — | Text is the reviewed translation to store. A human write always wins over the stored value. |
tier | string | — | — | — | Tier is the engine tier the entry belongs to, quality (the default) or bulk. Part of the entry's identity: the two tiers keep separate renderings. |
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.
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_translate_memory",
"arguments": {
"glossary": {},
"source": "<source>",
"state": "<state>",
"target": "<target>",
"text": "<text>",
"tier": "<tier>"
}
}
}'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 |
|---|---|---|---|
cloud_put_v1_translate_memory | PUT /v1/translate/memory | translate | Review records a human decision on one translation-memory entry, and returns the entry as… |
The same capability over plain HTTP is in the translate API reference, on https://api.hanzo.ai.
All 833 tools · The door · API reference
Generated from tools/list on https://api.hanzo.ai/v1/mcp — 833 tools captured 2026-08-01 (this build read the vendored copy; the door was unreachable).
How is this guide?