Hanzo
Cloud MCPunmapped

delete_v1_train_experiments_name

DeleteExperiment deletes a hyperparameter-tuning experiment. Kubernetes garbage-collects the Trials katib created under it, because they carry the Experiment as their owner.

DeleteExperiment deletes a hyperparameter-tuning experiment. Kubernetes garbage-collects the Trials katib created under it, because they carry the Experiment as their owner. Answers 204, or 404 for a name the caller's org does not own.

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

Arguments

FieldTypeRequiredDefaultValuesDescription
namestringName is the resource to act on, taken from the path. Lower-cased and trimmed to the DNS-1123 label a CustomResource's metadata.name must be.

tools/list declares a type and a description for each field and nothing further, and the OpenAPI document describes no operation for this tool. A above means neither source constrains the field, not that it is unconstrained in practice.

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

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

The door exposes delete_v1_train_experiments_name, 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