find_alternatives takes a product/SaaS name and returns a vetted list, while vet_repo takes an owner/name slug and returns a single verdict, so the input shapes clearly separate them. There is mild conceptual overlap since find_alternatives embeds repo vetting, and an agent holding a known repo URL might hesitate between the two.

Both tools use a consistent snake_case verb_noun pattern (find_alternatives, vet_repo). The verbs are distinct and accurately describe the action, with no mixing of conventions.

Two tools is thin for a server, though the scope (find alternatives, vet a repo) is genuinely narrow so nothing is padded. It sits at the borderline where a third operation like compare or get_repo_details would round out the surface.

The core workflow—discover alternatives and vet a specific candidate—is fully covered, including the key risk signals (abandonment, license, bus factor). Minor gaps exist: no side-by-side comparison of multiple alternatives or retrieval of raw repo metadata beyond the verdict.