MCP tools: Assistance
Last updated 17 days ago
MCP tools: Assistance
Tools that neither read nor write project data, but help the AI answer: product knowledge, the support path, and how things are rendered in chat.
search_docs
Searches the Liza documentation (what Liza is, how it works, the Public API and MCP). read · guest
The source is the very pages you are reading — the server ingests them as llms.txt/llms-full.txt from docs.liza.app.
create_feedback
Creates a post in Featurebase (feedback.liza.app) — the path for bug reports, feature requests, feedback and support.
The response contains the real post URL (feedback.liza.app/p/…). Do not create an internal list item and never invent a ticket ID.
get_widget_spec
Returns the specification of the Liza chat widgets. read · guest
Widgets are fenced code blocks that Liza renders in chat as real elements instead of text:
Call it before writing the first such block in a session instead of guessing the JSON schema.
Skills
The skill catalogue holds vetted, ready-made instructions for recurring tasks — maintained centrally and released per organization. The AI pulls them in by itself; these tools make them discoverable.
search_skills
Searches the catalogue. The best match comes back with its full instructions, so one call is usually enough. Without query it lists what exists.
get_skill
Fetches a skill by its slug. Without path you get the instructions plus the list of extra files; with path you get that one file.
Extra files only this way
There is no filesystem in an MCP session — Read does not work on these files. The way in is get_skill with path.
Was this helpful?
Still need help? Ask the team