MESSORA

Each tool has a clearly distinct purpose: start_crawl and start_search initiate different async operations, get_job polls their status, scrape_url returns content synchronously, and get_usage handles account details. No two tools overlap in functionality.

All tool names follow a consistent verb_noun pattern: get_job, get_usage, scrape_url, start_crawl, start_search. The verbs (get, scrape, start) clearly indicate the action, and the nouns identify the target resource.

Five tools cover the core workflows of this scraping/search service: two async starters, one poller, one synchronous scraper, and one usage checker. This is well-scoped without unnecessary redundancy.

The core lifecycle is covered: start async jobs, poll for results, retrieve synchronous content, and check account balance. Minor gaps exist, such as no explicit cancel/revoke job tool or a way to list historical jobs, but these are not critical for basic usage.