Memtrace Docs First

Memtrace Docs First

The Iron Law

IF THE USER ASKS ABOUT MEMTRACE PRODUCT DOCS → USE DOCS MCP TOOLS FIRST.
Do not guess CLI flags, MCP tool lists, enterprise deploy steps, or fleet rules
from memory. Query the hosted documentation corpus at memtrace.io (or
MEMTRACE_DOCS_API_URL), then answer with citations.

memtrace-first  = your indexed SOURCE CODE (find_code, get_impact, …)
memtrace-docs   = official MEMTRACE DOCUMENTATION (search_docs, ask_docs, read_doc)

Docs tools call the hosted Memtrace docs API over HTTPS. They do not read your local MemDB or your repo. Core graph tools stay offline; docs tools degrade gracefully when the network is down (ok: false + hint).

Server check (once per session)

Confirm the docs tools are available on your memtrace MCP server:

• search_docs — ranked chunks (slug, title, H2, excerpt)
• ask_docs — grounded Q&A { answer, citations[], refused }
• read_doc — full page text by slug
• Resources: memtrace://docs/<slug> via read_resource (optional)

If none of these exist, the MCP build may be outdated — tell the user to update Memtrace and run npx -y memtrace-skills@latest install.

Override API host: MEMTRACE_DOCS_API_URL (default https://memtrace.io).

The decision rule

| User is asking | Right tool | |---|---|---| | "How do I install / configure / deploy X in Memtrace?" | ask_docs(question=…) | | "What MCP tools / skills / CLI commands exist?" | ask_docs or search_docs then read_doc on hit slugs | | "What does memtrace rail enable do?" | ask_docs | | "Find docs about fleet coordination" | search_docs(query=…) |