Example prompts
Why this works
A single MCP call answers a narrow question. A chain across connectors produces a deliverable. The MCP layer is stateless per call, so the assistant can fan out and combine results freely in one turn. For each example above, the assistant typically:- Searches and fetches the relevant process from Within.
- Pulls observations and recent changes for current-state grounding.
- Hands the synthesized context to the second connector to take action.
Practical tips
- Name the deliverable, not the tool. “Draft an email” is better than “use Gmail” — let the assistant pick.
- Constrain by scope. “In our P2P value stream” or “owned by the finance team” gives the assistant a tractable subtree to walk.
- Ask for citations. Within tools return process IDs, observation timestamps, and artifact IDs. A good deliverable threads those back in so the recipient can verify.

