No user-submitted related servers found.
Scored across 16 tools
Each tool maps to a distinct stage or resource in the workflow: discovery, JD fetch, scoring, queue curation, resume build/verify/render, submission planning, and ledger read/write. Closely related tools like get_search_angle vs list_search_angles and discover_jobs vs list_queue are separated by lookup-vs-enumerate and new-discovery-vs-existing-queue.
Nearly all tools follow a clear verb_noun pattern using predictable verbs like list_, get_, fetch_, build_, render_, and record_. The only notable outlier is ledger_summary, which is a noun phrase rather than a verb-led name, but the overall convention is consistent and readable.
At 16 tools, the set is slightly above the typical 3-15 well-scoped range, but the count is justified by the breadth of an end-to-end job-search pipeline. Each tool covers a distinct step with little redundancy, so the size feels earned rather than bloated.
The surface covers the full core loop: discovery, curation, scoring, resume building/verification/rendering, submission planning, email verification, and application ledger recording. Minor lifecycle gaps exist, such as updating or withdrawing ledger entries and programmatically restoring parked roles, but these do not block the main workflow.