No user-submitted related servers found.
Scored across 10 tools
Each tool targets a distinct action: search (web_search), read text (read_url), save files (grab_site/fetch_asset), transcribe media, and a four-tool login lifecycle plus status. The only borderline pairs are grab_site vs fetch_asset and login_status vs login_check, but the descriptions explicitly cross-reference and delimit these (whole page vs single file, inventory vs one-page test). Boundaries are clear enough that an agent should pick correctly.
Most names are snake_case verb_noun (read_url, grab_site, fetch_asset), but the pattern is mixed: web_search is noun_verb, get_status uses get_ while the status-family uses a login_ prefix, and transcribe is a bare verb. Readable overall, but no single predictable convention across all ten.
Ten tools is well within the comfortable range and each maps to a real capability (status, search, read, two grab paths, transcribe, four login operations). No filler tools; the login cluster of four is large but each is a distinct operation.
Core workflows—search, read, asset save, transcription, login management, health check—are fully covered with sensible error paths. Minor gaps: no batch read of multiple URLs in one call, and no tool to inspect or change configuration/cached state beyond get_status.