DataRespublica

Each tool mostly targets a distinct artifact: commune fiche, département fiche, DVF prices, delinquency rate, rankings, proprietary scores, catalog, guidance, HATVP declarations. There is some conceptual overlap between get_commune (which already exposes fiscal/sécurité indicators), get_territory_scores, and get_delinquance_commune/get_ranking_head (delinquance, taxe-fonciere), which could cause a misselection when an agent just wants one indicator. The descriptions largely disambiguate by naming the underlying table/series, so the overlap is manageable.

Eight of nine tools follow a clean get_<resource> snake_case pattern, and list_hatvp_declarations follows the same verb_noun convention for a collection. The only minor inconsistency is prefixed French/English mixing (get_dvf_commune vs get_commune) but the structural pattern is predictable. No camelCase or vague verbs.

Nine tools is well within the ideal 3–15 range for a read-only territory-data server. Each tool maps to a distinct data product (fiche, DVF, delinquency, rankings, scores, catalog, guidance, HATVP) with no filler. Scope is tight and coherent.

The surface covers fiche-level reads, rankings, scores, and guidance, but there is no discovery/resolution tool to find a commune or département code from a name, and no region-level fiche despite commune/département coverage. It is also entirely read-only with no comparison or multi-territory query path, leaving agents to chain calls manually. These are workable gaps but notable for a territorial data server.