msl.mt.gov
success
Claude Code
intent
What does msl.mt.gov do and who is it for? Explain it back to me.
18steps
61.1sduration
$0.5980cost
140,385tokens
26 steps8 reasoning steps3 searches
home
docs
/services
docs
docs
docs
/services
docs
home
/licensing
/accessibility
search
/libraries
/research
search
/libraries/statewide_p…
/libraries/statewide_p…
search
73%
on-site discovery
80%
reliability
47%
link following
path origin
- previous resource47%
- web search27%
- prior knowledge27%
insight
The agent successfully compiled a comprehensive explanation of Montana State Library's mission, audience, pricing model, and differentiation, though it had to assemble this answer largely from web search results and prior knowledge rather than from clearly structured content on the site itself. The site's HTML responses were truncated during fetches, forcing reliance on search results and external sources; the agent ultimately synthesized information from search snippets, linked service pages, and general knowledge to answer the task.
- ›The agent's actual content came primarily from web search results (steps 15, 16, 24) rather than direct site navigation. Search snippets and linked URLs surfaced key service offerings (Montana Library2Go, OCLC Services, Libraries support) that individual page fetches could not deliver due to truncation.
- ›Site discoverability was fragmented: the site uses separate domains (msl.mt.gov vs. mslservices.mt.gov) and the main pages (/, /about, /libraries, /research) did not return complete, substantive content in the fetches—the agent noted this as confusing. Direct guesses at URLs like /services and /licensing returned 404s.
- ›Pricing information was sparse and scattered. The agent found references to EBSCO collection costs (~$57,810/year) and state FY 2025 allocations (~$1.4M) only via search results and external links (program budget PDF from archive.legmt.gov), not from a dedicated pricing or budget page on msl.mt.gov itself.
- ›The site is institution-centric rather than consumer-ready. Service pages exist (e.g., /libraries/statewide_projects/montanalibrary2go, /libraries/statewide_projects/oclc_services) but require prior knowledge of their URLs; there is no clear information architecture or navigation path that would allow an agent to systematically discover and extract this information.
- ›The agent's final answer included citations to six URLs, but only four are from msl.mt.gov proper (the other two are external). This indicates that msl.mt.gov alone does not publish sufficient structured, machine-readable information to answer the task without supplemental research.
See every agent that visits msl.mt.gov
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 →