> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.ada.cx/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.ada.cx/_mcp/server.

# get_glossary_conflict_guide

Returns a step-by-step recipe for detecting conflicts between the AI agent's glossary and the rest of its configuration — custom instructions, company description, coaching, and knowledge articles. A conflict is anything elsewhere in the configuration that contradicts, duplicates, or undermines a glossary term, so the agent would behave inconsistently.

The recipe is read-only: it tells the assistant which tools to call and how to classify and report what it finds, but it never changes any configuration.

Call this when asked to audit, review, or check the glossary for conflicts, duplicates, or contradictions — before reading the glossary, so the assistant follows the recommended workflow rather than improvising.

## Example prompts

* "Check my glossary for conflicts with my custom instructions."
* "Audit the glossary — are any terms contradicted elsewhere in my configuration?"
* "Is the term `group-plan` consistent with the rest of my Agent's setup?"

## Parameters

| Parameter | Type   | Required | Description                                                                                                               |
| --------- | ------ | -------- | ------------------------------------------------------------------------------------------------------------------------- |
| `scope`   | string | No       | What to check. Use `the entire glossary` (default) for a full sweep, or name a specific term / `external_id` to focus on. |

## Response

Returns markdown describing how to:

* **Load the glossary** with [`list_glossary_terms`](/mcp/tools/list-glossary-terms) (paginating until every term is fetched).
* **Load the other configuration** with [`get_ada_configuration`](/mcp/tools/get-ada-configuration) (company description, custom instructions, playbooks, web actions).
* **Cross-reference** each term against coaching and knowledge using [`search_coaching`](/mcp/tools/search-coaching) and [`search_knowledge`](/mcp/tools/search-knowledge).
* **Classify** conflicts into four types (behaviour defined elsewhere, heavy term usage, intra-glossary overlap, contradictory definitions).
* **Report** findings in a structured Glossary Conflict Report with a suggested resolution per conflict.