get_v1_help_articles
Returns the public knowledge base: the help center's Published, publicly-visible articles as cards.
Returns the public knowledge base: the help center's Published, publicly-visible articles as cards. The org is server-fixed and the status/is_public filter is server-set, so neither the tenant nor the visibility can be widened by the caller. A deployment with no help center answers 404.
| Tool | get_v1_help_articles |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 2 |
| Operation | GET /v1/help/articles |
| Product | help |
Arguments
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
category | string | — | — | Category narrows the list to one knowledge-base section, matched against the article's category by exact name. Empty lists every section. |
limit | integer | — | — | Limit caps how many articles are returned. Anything that is not a positive integer uses 50, and values above 200 are clamped to 200. |
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": "get_v1_help_articles",
"arguments": {
"category": "<category>",
"limit": 0
}
}
}'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_get_v1_help_articles | GET /v1/help/articles | help | Returns the public knowledge base: the help center's Published, publicly-visible articles |
The same capability over plain HTTP is in the help 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?