Summary
`version` is the whole argument for reaching for this instead of asking the model directly.
`python_get_documentation` and `k8s_get_documentation` take it, which is what makes an answer about a manifest or an API object checkable against the release in front of you rather than against whatever mix of releases the model absorbed. The surface is narrow by design — Python libraries and Kubernetes, with `top_k` deciding how much comes back — so it answers documentation questions and nothing adjacent to them.
What it is
A documentation retrieval surface for Python libraries and Kubernetes, answering a natural-language question against a version-aware index and returning the closest passages.
What you get
- Python answers scoped to a library and a release: `python_get_documentation` takes a natural-language `query` with `library` and `version`, and returns `top_k` passages from a documentation index consolidated from multiple sources into one searchable base.
- Kubernetes answers pinned to a cluster version: `k8s_get_documentation` takes a `query` about kubectl commands, API objects, manifests, controllers or version-specific features, with `version` and `top_k`, against a version-aware index drawn from sources including GitHub, DeepWiki and curated Kubernetes documentation.
Requirements
Nothing — no account, no key.
Setup effort
One command — npx -y @grounddocs/grounddocs@latest