search_my_truv
Searches MyTruv documentation for content matching your query. Returns matching pages with titles, snippets, and direct links. Use this when you need to find information without knowing the exact page path. Parameters:
Response fields:
Example prompt: “What security measures does MyTruv use?”
The tool is called with a query like
"security data protection" and returns matching pages such as How Your Data Is Protected, Is MyTruv Safe?, and Who Can See My Data?.
query_docs_filesystem_my_truv
Runs a read-only, shell-like command against a virtualized in-memory filesystem that contains only the MyTruv documentation pages and OpenAPI specs. Nothing runs on your machine or any server - it is a sandbox backed by documentation content. This is also how you read a full page: there is no separate “get page” tool. Parameters:
Supported commands:
rg, grep, find, tree, ls, cat, head, tail, stat, wc, sort, uniq, cut, sed, awk, jq, plus basic text utilities. No writes and no network access.
To read a page, pass its path with a leading slash and the .mdx extension, for example cat /billing/subscription-plans.mdx or head -80 /api-reference/overview.mdx. Each call is stateless: the working directory resets to / every time, so use absolute paths or chain commands with && in a single call.
Example prompt: “Show me the full page about subscription plans.”
The assistant runs cat /billing/subscription-plans.mdx and returns the complete content of that page.
submit_feedback
Reports a problem with a documentation page to the MyTruv docs team. Use it when a page is incorrect, outdated, confusing, or has a broken example. This is for feedback about the documentation itself, not product support. Parameters:
Example prompt: “The spending analysis example looks wrong, report it to the docs team.”