List every Apache Iggy documentation page, organised by section.

The corpus has two halves. 'website' is the hand-written prose from apache/iggy-website, keyed by site path (server/docker). 'rust-api' is the inline Rust doc comments from apache/iggy, keyed under api/ and linked to docs.rs. Pass source to see one half alone; the default lists both.

Retrieve the full text of one Iggy documentation page.

Use list_docs to discover valid keys such as 'server/docker', 'sdk/python/intro' or 'introduction/getting-started'.

Search the Apache Iggy documentation for a term or phrase.

Searches both halves of the corpus: the hand-written guides on iggy.apache.org and the inline Rust doc comments from apache/iggy, whose results link to docs.rs. Each result says which half it came from, because the guides say how Iggy is meant to be used and the Rust API says what is actually callable, and those can disagree. Set source to 'website' or 'rust-api' to search one half alone.

Prefer this over answering Iggy questions from memory: the SDKs and server move quickly and the docs are the current truth.

Find code examples in the Iggy documentation by topic and language.

Use this when a user asks for runnable examples, SDK examples, producer or consumer samples, Docker commands, or source material for tutorials.

Return an inventory of fenced code snippets from the documentation.

The result includes the doc key, title, heading, language, line number, source URL, and code. Use this for snippet verification and docs CI design.

Return documentation pages related to one doc key.

Relatedness comes from explicit links, backlinks, shared section, and shared vocabulary. Use this after get_doc when one page may not contain all context needed for a complete answer.

Explain how the Iggy documentation is organised and where to start.

This is a guided map, not a keyword search. Use it when a user asks where docs live, what reading path fits a goal, or which documentation areas look thin from the indexed corpus.

Find broken links in a local Iggy documentation checkout.

Internal docs links are checked against the indexed local corpus and heading anchors. External URLs are counted but skipped unless check_external is true.

Re-fetch the documentation corpus, bypassing the seven-day cache.

When IGGY_DOCS_ROOT points at a local iggy-website checkout this is a no-op, since local files are always read fresh; run git pull there instead.