Dadaville

Most tools target a clearly distinct resource: define (glossary), list_pages/list_persone/list_sedi (enumerations), get_persona/get_sede (entity profiles), get_ecosistema (graph), search. The one real overlap is fetch vs get_page, which both return Markdown of a dadaville.ch page and differ only in input form (url from search vs path), so an agent could reasonably pick the wrong one.

Six tools follow a clean verb_noun pattern (get_page, get_persona, get_sede, get_ecosistema, list_pages, list_persone, list_sedi), but define, fetch and search are bare verbs with no object, breaking the convention. Still readable, but mixed styles force the agent to infer semantics from descriptions rather than names.

Ten tools is well-scoped for a read-only cultural archive site: three list tools, three entity lookups, a glossary lookup, a search, and a graph view. Each tool maps to a genuine access pattern; nothing feels padded or missing at the count level.

There is coherent list+get coverage for pages, persone and sedi, plus global search and a graph endpoint, which covers the browsing domain well. Minor gaps: glossary terms can only be looked up by name (no listing or search) and search is scoped to pages, so entities may not be reachable by query text.