Skip to main content
Claude and ChatGPT both have web search built in. Combine that with the Within MCP and you get gap analysis that would take a human days to assemble. The pattern: Within tells the assistant what you actually do. Web research tells it what you should be doing. The gap writes itself.

​
Example prompts

​
Recipe

1

Ground in the workspace first

Call search → fetch → get_process_details to read the current state of the target process.
2

Surface the actual pain pattern

Call get_process_observations and get_observation_citation — your real deviations, not assumed ones.
3

Pull external context

Use the client’s web search — and any other tools available in your environment (browser, file search, internal knowledge bases) — to gather published frameworks, vendor positioning, or regulatory guidance.
4

Synthesize the gap

“Your process does X today, with these deviations. The framework recommends Y. The gap is Z — here’s the evidence for both sides.”

​
Watch for

  • Don’t anchor on web findings alone. The workspace is the ground truth. If a benchmark contradicts what observations show, the benchmark is the hypothesis.
  • Cite both sources. Process IDs, observation timestamps, and source URLs side by side. That’s what makes the gap analysis defensible.