No user-submitted related servers found.
Scored across 9 tools
The three search-family tools (search_procurements, search_procurements_detailed, search_awards) target genuinely different questions (open tenders vs. expanded hits vs. awarded contracts), and descriptions explicitly state when to pick each. However, search_procurements_detailed is a wrapper over search_procurements + get_procurement_details, so an agent could plausibly reach for the wrong one without reading carefully.
Nearly all tools follow a consistent snake_case verb_noun pattern (search_awards, get_procurement_details, find_procurement_office, search_cpv_codes). The lone exception is source_status, a noun phrase that breaks the verb-first convention but remains clear.
Nine tools is well-scoped for a procurement-search server, covering search, detail retrieval, history, code/canton resolution and health checks. Each tool earns its place with no obvious redundancy beyond the deliberate convenience wrappers.
Covers the full read lifecycle: keyword search, award filtering, full-record fetch, project history, plus the resolver tools (CPV, construction codes, offices) needed to build queries. As a read-only simap front-end it is thorough, though finer-grained capabilities like lot-level detail retrieval or bulk export are absent.