mcmaster.com
success
Claude Code
intent
What does mcmaster.com do and who is it for? Explain it back to me.
11steps
60.6sduration
$0.8619cost
93,196tokens
15 steps4 reasoning steps6 searches
home
docs
/shipping
search
/help
/company
search
search
search
search
search
100%
on-site discovery
100%
reliability
40%
link following
path origin
- previous resource40%
- prior knowledge60%
insight
The agent assembled a comprehensive explanation of McMaster-Carr by combining prior knowledge with web search results, since the website itself returned only structural HTML without accessible content. The agent successfully answered what McMaster-Carr does, who it serves, how it's priced, and how it differs from competitors—but had to work around a largely inaccessible website by relying on external sources (Wikipedia, Harvard case study, industry comparison sites) rather than primary content from mcmaster.com itself.
- ›Steps [1], [3], [4], [6], [7] fetched the actual McMaster-Carr website but returned only HTML scaffolding with meta tags—no navigable content, pricing details, shipping information, or company background. The site is JavaScript-rendered and does not expose content via direct HTML fetches.
- ›Steps [8]–[13] were content-bearing web searches that supplied nearly all substantive information in the final answer: business model, revenue, employee count, distribution center locations, competitor comparisons, pricing strategy, target customers, and product categories. These external sources (Wikipedia, Harvard case study, Owler, industry comparison sites) were cited in the Sources section and formed the backbone of the response.
- ›The agent explicitly flagged that McMaster-Carr's own website is deliberately opaque about shipping costs and pricing—this insight came from search results mentioning user frustration, not from mcmaster.com itself. The site's intentional design to hide shipping rates until checkout is documented in external sources, not on the primary domain.
- ›McMaster-Carr's website is poorly navigable for agent-based discovery: it relies entirely on JavaScript interactivity, client-side rendering, and dynamic content. Direct URL guessing (/about, /shipping, /company, /help) yielded no useful content. The agent could not reach product categories, pricing pages, or policy documentation through the website's own navigation.
- ›60% of the final answer was derived from prior knowledge and external web search (40% prior knowledge, 0% web search per the config, but the agent made 6 substantial web searches [8]–[13] that were cited). The official website contributed no substantive content to the final response despite being the primary source domain.
See every agent that visits mcmaster.com
Front builds the agent version of your site and shows which agents visit, what they came for, and what your pages couldn't answer.
or talk to us about agent readiness →