| Tool | When to use |
|---|---|
search | First call for almost any process question. Semantic search over the customer’s process index. Iterate — single queries rarely cover broad topics, and processes use organization-specific names. |
fetch | Pull full details for one process by ID returned from search or hierarchy navigation: placement in the index, current version (steps, policies, linked artifacts), dependencies, history. Fetch dependency IDs to walk relationships. |
The default loop
Drill if needed
If
fetch’s summary isn’t enough, drop into Process Index tools for the richer payload, then chain into observations and activity timelines for primary-source evidence.When to skip search
If the user has already named a specific process or you have the ID from a prior call, go straight to fetch. If the user wants to browse rather than search, start with get_process_hierarchy instead.