Hanzo
Cloud MCPunmapped

get_v1_train_jobs

ListJobs lists the training jobs in the caller's org.

ListJobs lists the training jobs in the caller's org. Each entry carries the job's name, when Kubernetes admitted it, and the trainer operator's live status — the spec is on the single-job read.

Toolget_v1_train_jobs
Doorhttps://api.hanzo.ai/v1/mcp
Methodtools/call (JSON-RPC 2.0)
Arguments0
Operationnone in the OpenAPI document
Product

Arguments

This tool declares no arguments. Call it with an empty arguments object.

Call it

A tools/call carries its arguments in one flat object. This tool declares none, so the object is empty.

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": "get_v1_train_jobs",
         "arguments": {}
       }
     }'

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

The door exposes get_v1_train_jobs, but the copy of the OpenAPI document this build holds (pinned at 4e41f04ca) describes no operation for it — neither under that name nor at the route the name implies. That is either a route the document has yet to declare, or one the door has renamed since the pin. Everything on this page comes from tools/list; there is no REST reference to link to until the two agree.


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

How is this guide?

On this page