> For the complete documentation index, see [llms.txt](https://docs.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.distro.so/developers/assistant-recipes.md). # Useful requests for an AI assistant After connecting [Distro MCP](/developers/mcp.md), start with specific questions that the available tools can answer. ## Explain an assignment “Find assignments for this lead email. Show the queue, eligible members, rotation evidence and why the winner was selected.” The assistant can combine assignment lookup/log/explanation tools. Ask it to distinguish recorded evidence from its interpretation. ## Investigate a failed workflow “Find the latest failed runs for this workflow. Read the input and ordered step logs, then explain the first failure.” A diagnosis should include the failing step and provider error. An assistant's explanation is not evidence that the failed provider write was repaired. ## Find missing mappings “Show mapping coverage and members without the CRM owner or sales-tool identity this workflow needs.” Review the affected members before changing identities in the app. ## Prepare a change “Preview pausing this member in this queue. Show the current state and proposed state before applying.” Supported writes require the tool's apply path. After applying, read the resource again and verify the result. ## Prepare record work “Inspect the person schema, find these stored records and preview the Fill gaps batch with the chosen provider.” Records tools inspect stored Distro data, not an arbitrary live CRM search. Review provider usage and the eventual batch results. Use [MCP tool catalog](/developers/mcp-tools.md) to keep requests within available capabilities. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.distro.so/developers/assistant-recipes.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.