List help topics
knowledgebase_listList every question the customer knowledge base can answer — how the service works, what we offer, design, artwork files, ordering, payment, delivery, privacy.
Call this before answering a question about how the service works or what its
policies are — even one that sounds obvious ("do I need an account?", "can I cancel
after paying?", "what resolution should my images be?"). The entry is the source for
this business's policies. Read the index, pick the entry whose question
matches theirs, then call knowledgebase_get with its entry_id and answer from that
entry. If no question matches, say you don't have that information — never state a
policy the corpus does not contain.
The test is whether answering needs a LIVE LOOKUP. If the true answer would differ per
product, per job or per order, it is not in here: what sizes or options a product comes
in, whether you print a particular thing, what a configured job costs, the turnaround on
an offer you already quoted, where a given order stands, the exact bleed measurement for
an order's artwork (a general bleed question — "do I need bleed?", "what bleed?" — is a
question for here). Those come from catalog_search/catalog_get_schema, order_get_quote,
order_get_artwork_spec and order_get/order_lookup. Everything that is the same
answer for every customer — delivery, refunds, design ownership, whether they can supply
their own logo or artwork, what file formats we take — is a question for here, even when
the answer involves numbers. A general question that names no order or product yet (how
to track a parcel or check an order, whether a sample is possible, the smallest order) is
a question for here too, even when it reads like a request to look one up: read the entry
first, then offer the lookup or ask which product. But an order the customer names by its
reference is a live lookup, however general it sounds: look that order up and read no
entry. Read at most ONE entry per question —
the index gives you
enough to pick the right one — and don't look it up again later in the conversation.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"session_id": "<session_id>"
},
"name": "knowledgebase_list"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| session_id | Yes |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |