patch_v1_tools_catalog_id

CurateListing sets what WE say about one catalog entry — hidden, featured, official, logo — and answers with the stored listing. SuperAdmin only; every other caller is refused.

Curation is the half of a catalog row a sync cannot write, and this is the only thing that writes it. The upstream half is never editable here: a description that disagreed with the publisher's would be a fork of their listing, and the next sync would silently undo it.


Tool	`patch_v1_tools_catalog_id`
Door	`https://api.hanzo.ai/v1/mcp`
Method	`tools/call` (JSON-RPC 2.0)
Arguments	5
Operation	`PATCH /v1/tools/catalog/{id}`
Product	tools

Arguments

Field	Type	Required	Default	Description
`featured`	`boolean`	—	—	Featured puts the listing on the front of the shelf, or takes it off.
`hidden`	`boolean`	—	—	Hidden takes the listing off the org-visible shelf, or puts it back.
`id`	`string`	—	—	ID is the listing to curate, from the path.
`logo`	`string`	—	—	Logo is the brand mark to render, an https URL. Empty clears ours and lets the next sync adopt the publisher's own icon again.
`official`	`boolean`	—	—	Official overrides the derivation: setting it makes this answer FINAL, so no later sync re-derives over it. That is the difference between a default and a decision — the derivation can only tell that a domain-verified publisher serves the endpoint, not that the product is theirs.

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_tools_catalog_id",
         "arguments": {
           "featured": false,
           "hidden": false,
           "id": "<id>",
           "logo": "<logo>",
           "official": false
         }
       }
     }'

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_tools_catalog_id`	`PATCH /v1/tools/catalog/{id}`	tools	CurateListing sets what WE say about one catalog entry — hidden, featured, official, logo

The same capability over plain HTTP is in the tools 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).

patch_v1_tools_catalog_id

Arguments

Call it

The operation behind it

On this page