Scored across 7 tools
The two discovery/listing tools (list_servers vs list_families) and the two catalogue tools (search vs describe) have some conceptual overlap, but descriptions clearly delineate them (catalogue-wide routing vs per-family readiness vs discovery vs schema inspection). The action tools validate/generate/parse are cleanly separated by direction and intent.
All names are lowercase consistent verbs, and the two multi-word names (list_servers, list_families) follow a clean verb_noun pattern. Minor deviation between bare verbs (search, describe, validate, generate, parse) and the list_* pair, but still highly predictable.
Seven tools is well-scoped for a gateway/orchestration layer whose job is discovery, schema inspection, and dispatching parse/generate/validate. Each tool earns its place with no filler.
The surface covers the full discovery-to-execution lifecycle (search, describe, list_*, validate, generate, parse). The generate/parse asymmetry across families is intentional and documented, though the absence of any pain/acmt parsing path leaves a slight round-trip gap that agents must work around.