No user-submitted related servers found.
Scored across 88 tools
The extensive descriptions do a lot of work distinguishing overlapping tools (tailor_application vs edit_application, update_base_resume vs edit_base_resume), but genuine confusion remains. The proposal state-machine tools (record_decision, request_decision, record_triage, record_consent, resume_proposal) and pairs like attach_evidence vs attach_evidence_file, score_ats vs compare_ats require careful reading to select correctly.
Almost everything is snake_case with a verb_noun shape (list_jobs, create_base_resume, kb_edit_point, render_pdf), and prefixes cleanly partition domains (kb_*, explore_*). A few names drop the noun (quick_tailor, sync_now, process-free but verb-only) and ingestion verbs vary (kb_ingest_resume / store_extracted_jd / kb_capture), but the overall convention is predictable.
88 tools is far beyond the 25+ heavy threshold and forces an agent to navigate a very large surface. The career-studio domain is genuinely broad (KB, resumes, tailoring, scoring, rendering, templates, job capture, proposals, evidence, automation), so most tools earn a place, but the set could plausibly be consolidated into a smaller, more navigable surface.
Coverage is unusually thorough: full CRUD on resumes, KB entities/points, templates, applications, proposals, plus scoring, health checks, rendering, evidence, and automation lifecycle. Minor documented gaps remain that force fallbacks to the web UI (cannot clear application fields to null, disputes/word bank web-only, certificate PDF upload), but the core workflows are complete.