deploy
deploy: 11 operations.
deploy: 11 operations. Name one in "op" and pass that operation's own arguments in "input". describe returns an operation's input schema.
| Tool | deploy |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 2, 1 required |
| Operation | GET /v1/deploy/session/userinfo · GET /v1/deploy/version |
| Product | deploy |
Arguments
| Field | Type | Required | Default | Values | Description |
|---|---|---|---|---|---|
input | object | — | — | — | arguments for the chosen op |
op | string | yes | — | — | list_deploy_applications — Returns the fleet as an argocd ApplicationList: one projected Application per operator App CR, carrying the image tag… get_deploy_application — Returns ONE projected argocd Application by name, with status.resources filled in from its reconciled resource tree… get_deploy_application_resource_tree — Returns one application's argocd ApplicationTree: the objects the operator reconciled from its App CR, reached by… get_deploy_application_revision_metadata — Returns the argocd RevisionMetadata for one revision of one application — what the detail view shows beside a… list_deploy_application_syncwindows — Returns one application's argocd ApplicationSyncWindowState — the answer to "is anything blocking a sync of this… list_deploy_clusters — Returns the argocd ClusterList of the destinations the caller's applications reconcile into: one entry per distinct… list_deploy_gitops — Lists every Hanzo CD Application in the cluster: the git source each one polls, the commit it last APPLIED, how its… list_deploy_projects — Returns the argocd AppProjectList this console groups and filters applications by. get_deploy_session_userinfo — Answers "is this browser signed in, and if not where does it sign in?" — the dashboard SPA's bootstrap question, and… list_deploy_settings — Returns the argocd AuthSettings object the dashboard SPA awaits before its first render. get_deploy_version — Returns the argocd VersionMessage the dashboard SPA reads at bootstrap. |
tools/list declares a type, a description, which fields are required and an enumerated value set for each field and nothing further, and every column above is the door's own. This tool takes an operation name and that operation's arguments, so what the document constrains is what goes inside input, field by field, on the operation you name — ask describe for that. A — means the door does not constrain the field.
Call it
A tools/call carries every argument in one flat object — nothing binds to a path or a query string. This call carries exactly the arguments the operation requires, so it is the smallest one that can run.
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": "deploy",
"arguments": {
"op": "list_deploy_applications"
}
}
}'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
deploy dispatches to 11 operations. 2 of them the door names exactly as the document ids them, and those are below; for the rest the door has its own verb, which describe resolves.
| Operation | Route | Product | Summary |
|---|---|---|---|
get_deploy_session_userinfo | GET /v1/deploy/session/userinfo | deploy | Answers "is this browser signed in, and if not where does it sign in?" — the dashboard… |
get_deploy_version | GET /v1/deploy/version | deploy | Returns the argocd VersionMessage the dashboard SPA reads at bootstrap. |
The same capability over plain HTTP is in the deploy API reference, on https://api.hanzo.ai.
How is this guide?