Hanzo
Cloud MCPbooks

post_v1_books_ask

AskBooks answers a plain-language question about the caller's own books — "what is my MRR?", "how long is my runway?" — with figures taken from their ledger, never a guessed number.

AskBooks answers a plain-language question about the caller's own books — "what is my MRR?", "how long is my runway?" — with figures taken from their ledger, never a guessed number. A deterministic keyword router picks the intent and reads the real metrics, and those figures, followups and report sources are computed BEFORE any model call and are never altered by one: the optional narration seam only rephrases the sentence, and it degrades silently to the templated answer when no AI plane is wired. It is strictly read-only — it restates the books, it never posts to them.

Toolpost_v1_books_ask
Doorhttps://api.hanzo.ai/v1/mcp
Methodtools/call (JSON-RPC 2.0)
Arguments3
OperationPOST /v1/books/ask
Productbooks

Arguments

FieldTypeRequiredDefaultValuesDescription
fromstringFrom is the RFC3339 start of the metric window. Empty means all time, treated as a single reporting period (see monthsBetween).
questionstringQuestion is the plain-language question about the org's books, e.g. "what is my MRR?". Longer than 2000 characters is truncated, never refused.
tostringTo is the RFC3339 end of the metric window. Empty means up to now.

tools/list declares a type and a description for each field and nothing further. A means neither the door nor that operation constrains the field.

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": "post_v1_books_ask",
         "arguments": {
           "from": "<from>",
           "question": "<question>",
           "to": "<to>"
         }
       }
     }'

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

OperationRouteProductSummary
post_v1_books_askPOST /v1/books/askbooksAnswers a plain-language question about the caller's own books — "what is my MRR?", "how…

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


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