The Atlan MCP Cookbook

Grow your business glossary

Bootstrap glossary terms from how your assets already use business concepts.

All recipes

On the menu

Use case
Make data understandable
Action
Make changes
Persona
Data Governance Lead, Data/BI Analyst
Effort
Moderate
Runs in
any AI tool

The task

Scenario. "Customer lifetime value" shows up in a dozen tables, three dashboards, and half your dbt models, spelled LTV in some and CLV in others, and it has no canonical definition anywhere. You want a real term in the glossary, drafted from how the concept is actually used, with the relevant assets linked to it.

The ask

  • Every asset that references customer lifetime value or LTV
  • A definition drafted from how those assets use it
  • A glossary term created and the assets linked to it

Hero prompt

Hero prompt

Find all assets that reference customer lifetime value or LTV. Create a glossary term called Customer Lifetime Value with a definition based on how these assets use it, then link them to the term.

Step by step

  1. Search for assets that reference the concept.

    Step 1

    Find all assets that reference <concept, e.g. customer lifetime value>.

  2. Draft a definition from how it's used across those assets.

    Step 2

    Draft a definition based on how these assets use it.

  3. Create the term and link the relevant assets to it.

    Step 3

    Create a glossary term called <name> and link these assets to it.

What you'll give it

Required context

  • The business concept to bootstrap (and its aliases: LTV, CLV)
  • Glossary creation permission
  • A glossary to create the term in

Optional context

  • A preferred definition style (one sentence, or definition plus formula)
  • Any assets to exclude, such as sandbox or test tables

What Atlan creates

Outputs

  • The set of assets that reference the concept, by name and type
  • A draft definition of Customer Lifetime Value, written from that usage
  • The glossary term created, with the assets linked to it

Summary. You edit a first draft instead of starting from a blank page, and the term ships linked to the assets that actually use it, so the definition is discoverable the moment someone lands on one of them.

Writes to Atlan

Changed: a new glossary term, and glossary links on the matched assets. Left untouched: the asset descriptions and the data; only the link is added.

Follow-up prompts

Keep going once the first answer lands.

Do the next concept

Do the next concept

Now the same for "active user," and note where the definition looks inconsistent across assets.

Sharpen the definition

Sharpen the definition

Rewrite the definition to one sentence a new analyst would understand, and add the formula the tables use.

Fill the gaps

Fill the gaps

List assets that clearly use this concept but do not name it, so I can decide whether to link them.

Tips & troubleshooting

Cook's note

Let Atlan write the first draft of the definition. You edit; you don't start from a blank page.

  • Match the tool to the work. Definitions read better from a model built for close reading; use a more capable model, review the draft, then create the term.
  • Automate or chain it. Run it as a monthly sweep for undefined high-use concepts, so the glossary grows from real usage instead of a backlog.
  • Ask what it changed. Add "list the term you created and every asset you linked." A new term and its links are worth confirming.
THE ATLAN MCP COOKBOOK

Point your AI at the Atlan MCP.
Run your first recipe.

[Website env: production]