No user-submitted related servers found.
Scored across 2 tools
web_search and read_page target clearly different actions (discovery vs. full-content retrieval) with no overlap in purpose. An agent can unambiguously pick the right tool based on whether it needs to find URLs or extract content from a known URL.
Both names use snake_case and concise English, but the conventions differ slightly: 'web_search' is a noun-prefixed verb while 'read_page' is a verb-noun pair. It is still readable and predictable enough that the minor deviation doesn't hinder selection.
Two tools is thin for a general-purpose web access server; search plus read is the minimal viable pair. It is defensible for the stated scope but leaves no room for adjacent operations, making it borderline under-scoped rather than well-provisioned.
The search-then-read lifecycle is fully covered, and the read tool handles HTML, PDF, text, JSON, retries, and truncation, which is thorough. Minor gaps exist (no multi-URL batch read or explicit raw/headers fetch), but agents can work around them via sequential calls.