Search and read romankryvolapov.com engineering articles; message the author.
Scored across 4 tools
fetch and get_page perform the same operation on the same content — the get_page description literally says 'The same as fetch' — differing only in identifier type (search-result id vs canonical URL), which is a boundary an agent will easily trip over. search and send_message are clearly distinct, but a near-duplicate pair in a four-tool set is a significant ambiguity.
Pattern is broadly verb or verb_noun (search, fetch, get_page, send_message), but fetch vs get_page use different verbs and different granularity for what is essentially the same retrieve operation. Readable, but not a predictable convention.
Four tools is thin for the purpose, and because fetch/get_page are redundant the effective surface is really three. A single search, a single read, and a contact tool is defensible but borderline sparse.
Core lifecycle (search → read → contact author) is covered, but there is no way to list recent articles, browse by tag/language, or discover the corpus without an explicit query. Agents can work around it via search, but discovery is weaker than it should be.
Return the full text of one article by the id from search results (its canonical URL), as markdown with code listings preserved verbatim.
Inputs: id (required). Returns: id, url, text, title, +1 more
Return the full markdown of one article by its canonical URL (e.g. https://romankryvolapov.com/ru/ktor-manual/). Code listings are preserved verbatim. The same as fetch, as plain text.
Inputs: url (required).
Search the romankryvolapov.com engineering blog: articles on Java, Kotlin, Android, Spring, microservices, gRPC, Kubernetes, databases, and running large language models locally (llama.cpp, LoRA fine-tuning, RAG, prompt engineering). Every article exists in English, Russian and Ukrainian, and results come in one language: set lang to the user’s language, otherwise it is guessed from the query. Returns matching articles with snippets and URLs; read one with fetch, passing its id.
Inputs: query (required), lang, limit. Returns: results
Send a message to Roman Kryvolapov, the author of this blog: a question about one of the articles, a suggestion for a new article, or a job or project offer. It goes to his inbox, and he replies by email to the address given. Use it only when the user asked to contact the author, with the user’s own name and email address — never invent them — and show the user the text before sending. At most 20 messages a day are accepted from all agents together, and 3 from one email address.
Inputs: name (required), email (required), message (required), lang. Returns: sent, message
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Search and read bard0 design's FPGA and embedded engineering articles and site pages.
Search and read Skillaria.Top courses (AI, DevOps, Linux, Git) and guides in 20 languages.
Search and read Lynta's public documentation.
Search and read the Radixia blog (enterprise AI, cloud, open source) via MCP.
Add one secure layer between your agents and this server.
