Beacon by EVAA

Each tool targets a distinct concern: get_overview covers the company, list_offers covers services, list_resources lists articles, and get_resource fetches one article by slug. The list/get pairing is explicit (get_resource references the slug from list_resources), and overview vs offers are clearly separated despite both being company-related.

All four tools follow a clean verb_noun pattern (get_overview, get_resource, list_offers, list_resources). The get/list verbs map predictably to singular-vs-collection semantics, leaving no naming ambiguity.

Four tools is reasonable and each earns its place with no redundancy, but the surface is on the thin side for the domain. Adding a search or contact/inquiry tool would round it out without bloat.

A read-only brochure server covering overview, offers, and an article list+fetch is largely complete for its stated purpose. Minor gaps exist (no article search/tag filtering, no contact or inquiry action), but the core informational workflow has no dead ends.