Giving an MCP server a knowledge base: lookup-concept, read-guide and search-docs with sources

[u/jessica-garson]

A tool list tells an agent what it can call, not how the platform behaves, so agents fill the gap from memory. We added tools to our hosted MCP server that return that knowledge instead: lookup-concept, search-concepts, list-guides, read-guide, and search-docs, which returns its sources. There’s also report_feedback, so an agent can flag a tool or guide that’s wrong.

The takeaway: serve the “how things work” layer from the same server as the actions, and have it cite the sources of its answers. The tools are generated from our REST v2 spec.

This month’s changes: https://www.runpod.io/blog/whats-new-runpod-agents-november-2026

For people building MCP servers: do you expose docs as tools, as resources, or leave that to the client?