Guide

guide: 13 operations.

Also for this capability: API · CLI · MCP · SDKs

guide: 13 operations. Name one in "op" and pass that operation's own arguments in "input". describe returns an operation's input schema.

Tool	`guide`
Address	`https://api.hanzo.ai/v1/mcp`
Method	`tools/call` (JSON-RPC 2.0)
Arguments	2, 1 required
Operation	`DELETE /v1/guide/curriculum` · `GET /v1/guide/curriculum` · `GET /v1/guide/profile` · `GET /v1/guide/suggest`
Product	guide

Arguments

Field	Type	Required	Default	Values	Description
`input`	`object`	—	—	—	arguments for the chosen op
`op`	`string`	yes	—	—	—

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 MCP'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 MCP 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": "guide",
         "arguments": {
           "op": "list_guides"
         }
       }
     }'

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 MCP 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

guide dispatches to 13 operations. 4 of them MCP names exactly as the document ids them, and those are below; for the rest MCP has its own verb, which describe resolves.

Operation	Route	Product	Summary
`delete_guide_curriculum`	`DELETE /v1/guide/curriculum`	guide	Clears the caller org's curriculum override and returns the journey it falls back to — the brand blueprint, else the embedded fixture.
`get_guide_curriculum`	`GET /v1/guide/curriculum`	guide	Returns the journey the caller's org is actually running, and whether it comes from the org's OWN override (custom) or from the platform default — the brand blueprint, else the embedded fixture.
`get_guide_profile`	`GET /v1/guide/profile`	guide	Returns the caller org's OBSERVED growth profile — the signal set, the classified growth stage, and the org's own key metrics.
`get_guide_suggest`	`GET /v1/guide/suggest`	guide	Returns the caller org's next-best quests: the available, non-terminal steps of its journey ranked by how much downstream work each unblocks, each with the grounded reason it is a good next move and whether the Business AI can run it, plus the org's funnel and the GTM recommendations derived from it.

The same capability over plain HTTP is in the guide API reference, on https://api.hanzo.ai.

All 120 tools · MCP · API reference

Generated from tools/list on https://api.hanzo.ai/v1/mcp — 120 tools captured 2026-09-30.

Was this page useful?

PreviousGraph NextIAM