> For the complete documentation index, see [llms.txt](https://developer.frontitude.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.frontitude.com/mcp/getting-good-results.md). # Getting good results Tell your agent where to look. It starts every conversation knowing nothing about your workspace — not your projects, not your library, not the names you use. These are the things that help most. ## Name the place you mean Say which project, page, frame or category the job is about. The name you see in the app is enough to search on. If you name a page together with its project, and a frame together with its page, your agent finds the right one faster. Without a place to start, it could open your projects one at a time looking for the one you meant. ## Ask it to count before it lists Your agent can count what's in a place, broken down by status, language or category. The count tells you whether you're dealing with 12 texts or 4,000. It also saves your agent pulling page after page of results to find out. ## Ask to see the change before it lands Creating components has a dry run. Your agent reports what it would create and writes none of it. The riskier writes go further. They don't run unless your agent first says how many items it expects to change, or what copy it read. It's a guard against a change bigger than you meant. Before any other write, ask your agent to list what it plans to touch and wait for your go-ahead. Copy your agent writes stays in the item's edit history, so you can see what changed. A delete takes the history with it. ## Search finds library copy, not texts in a project Ask for a search when you want to know whether the wording already exists. Search matches on meaning and covers the copy library. Ask for a list when you want everything in a project, page or frame on one screen. Your agent can filter that list by status, language, tag, and whether a text is attached to a component. A search returns its best matches and stops there. If the right one isn't among them, ask for a narrower search rather than more results. ## Give a connection only the tools the job needs An agent that only audits needs the read tools and nothing else. Open ***Tools*** on the connection and clear everything that changes content. [Managing your connections](/mcp/authorization.md) walks through it. ## Source language edits reset translations Frontitude makes every translation from the source wording as it stood at the time. Change that wording and the translations are based on copy that no longer exists, so they all go back for retranslation. {% hint style="warning" %} Decide up front whether you want the source edit, the translation edit, or both, and tell your agent which. {% endhint %} --- # 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://developer.frontitude.com/mcp/getting-good-results.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.