The one that earns its keep is delete_knowledge: when a bot gives a wrong answer, the fix is almost always removing a stale chunk, not adding a new one on top.
Real prompts, not pseudo-code. Claude picks the tools itself.
| Tool | Needs | What it does |
|---|---|---|
list_knowledge | read | Everything a bot has been taught, by source. |
add_knowledge | write | Teach the bot a new fact, policy or document. |
delete_knowledge | write | Remove one chunk by id — the fix for an answer that went stale. |
list_knowledge_chunks | read | The retrievable pieces, so you can find the one that is wrong. |
add_website | write | Crawl a URL and turn its pages into citable knowledge. |
resync_website | write | Re-crawl after you have changed the site. |
list_help_articles | read | Published help centre articles. |
upsert_help_article | write | Write an article. It serves readers for SEO and teaches the bot at the same time. |
reorder_help_articles | write | Pull the articles that matter to the top. |
list_files | read | The PDFs and voice notes the AI can send, and how often each went out. |
add_file | write | Add a course PDF, price sheet or voice note from a link, and say when to send it. |
update_file | write | Change which course a file is for, when it goes out, or pause it. |
delete_file | write | Remove a file so the AI stops sending it. |
set_file_library | write | Let the AI send files by itself, or stop it. |
read works with any key. write is refused unless the key allows it — the server checks before the tool runs, so a read-only key genuinely cannot change anything.
Worth knowing before you wire it into something that matters.