patch_v1_agents_ref
UpdateAgent changes an agent in place. Every field is optional; a field the request omits keeps its stored value.
UpdateAgent changes an agent in place. Every field is optional; a field the request omits keeps its stored value. The resulting mode+schedule are re-validated together, so a partial update can never leave a long-running agent without the cron the scheduler needs to fire it, and a transition INTO long-running counts against the per-org cap on scheduled agents.
| Tool | patch_v1_agents_ref |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 9 |
| Operation | PATCH /v1/agents/{ref} |
| Product | agents |
Arguments
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
computeRef | string | — | — | — |
description | string | — | — | — |
executionMode | string | — | — | — |
instructions | string | — | — | — |
model | string | — | — | — |
ref | string | — | — | Ref is the agent to update — its public id or org-unique name, from the path. |
schedule | string | — | — | — |
serviceAccountId | string | — | — | — |
tools | string[] | — | — | — |
This tool's schema does not declare which fields are required, nor any default, nor any enumerated value set. The columns above are empty because the door publishes nothing there, not because the answer is "none" — where a field is constrained, the constraint is stated in that field's own description.
Call it
A tools/call carries every argument in one flat object — nothing binds to a path or a query string. Every declared argument is shown, because the door marks none of them required.
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": "patch_v1_agents_ref",
"arguments": {
"computeRef": "<computeRef>",
"description": "<description>",
"executionMode": "<executionMode>",
"instructions": "<instructions>",
"model": "<model>",
"ref": "<ref>",
"schedule": "<schedule>",
"serviceAccountId": "<serviceAccountId>",
"tools": [
"<tools>"
]
}
}
}'Values are placeholders derived from each field's declared type. 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_patch_v1_agents_ref | PATCH /v1/agents/{ref} | agents | UpdateAgent changes an agent in place. |
The same capability over plain HTTP is in the agents API reference, on https://api.hanzo.ai.
All 834 tools · The door · API reference
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?