Skip to main content
Glama

TOISE — intelligence foncière

Trouver des communes par critères

toise_communes_cibles
Read-onlyIdempotent

Quelles communes cibler, ou quels indicateurs socio-économiques d'une commune (population, revenus, prix au m², établissements, vacance) : filtre sur toute la France. Restreindre : departement ; comparer des adresses : toise_comparer_zones. Département par foncier institutionnel : toise_maillage ; trous de réseau : toise_cannibalisation.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "toise_communes_cibles"
  }
}

Input Schema

NameRequiredDescriptionDefault
triNoValeur affichée servant au tri…
ordreNo
limiteNo
curseurNo
decalageNo
revenu_maxNoRevenu médian annuel par unité de…
revenu_minNoRevenu médian annuel par unité de…
departementNo
prix_m2_maxNoPrix médian DVF au m² (€), au plus.
prix_m2_minNoPrix médian DVF au m² (€), au moins…
vacants_maxNoPart de logements vacants en %, au plus.
vacants_minNoPart de logements vacants en %, au moins.
prix_m2_typeNoType de bien du prix médian : logement…
revenu_regleNoComment comparer la fourchette d'IRIS au…
population_maxNoHabitants, au plus.
population_minNoHabitants, au moins.
etablissements_maxNoÉtablissements actifs (INSEE SIDE 2024), au…
etablissements_minNoÉtablissements actifs (INSEE SIDE 2024), au…
procedure_en_coursNoExige departement : 'avec' ne garde que les…

Output Schema

NameRequiredDescriptionDefault
triNo
liensNoLiens vers la fiche TOISE et vers des services de…
quotaNoQuota du jour après cet appel : { fonction, limite…
totalYesCommunes évaluables correspondant aux critères, AVANT…
limiteNo
curseurYes
partielNotrue : une source n’a pas répondu, des champs manquent…
sourcesYes
suivantNoDécalage de la page suivante (nom historique) ; null s’il…
communesYes
criteresNoCritères effectivement appliqués.
decalageNo
has_moreYes
visiteurNoNon nul sans compte : aperçu plafonné, avec motif.
warningsYes
renvoyeesNo
motif_videNoMotif quand la liste est vide.
definitionsNo
non_evalueesNoPar critère (revenu, vacants, etablissements, prix_m2) : {…
quota_unitesNoUnités d’usage du jour : consommees_par_cet_appel…
champs_absentsNoDonnées absentes du résultat partiel.
limite_atteinteNoPrésent quand un quota, une limite d’offre ou une fonction…
paiement_requisNoPrésent quand le résultat complet est un achat à l’acte…
criteres_indisponiblesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / prix_m2_min / description
      Previous value: -"Prix médian DVF au m² (€), au moins ; communes…"New value: +"Prix médian DVF au m² (€), au moins…"
    • changedInput schema / properties / prix_m2_type / description
      Previous value: -"Type de bien du prix médian : logement (défaut)…"New value: +"Type de bien du prix médian : logement…"
    • changedInput schema / properties / revenu_max / description
      Previous value: -"Revenu médian annuel par unité de consommation…"New value: +"Revenu médian annuel par unité de…"
    • changedInput schema / properties / revenu_min / description
      Previous value: -"Revenu médian annuel par unité de consommation…"New value: +"Revenu médian annuel par unité de…"
    • changedInput schema / properties / revenu_regle / description
      Previous value: -"Comment comparer la fourchette d'IRIS au seuil…"New value: +"Comment comparer la fourchette d'IRIS au…"
  2. Changed3 schema fields changed
    • changedInput schema / properties / etablissements_max / description
      Previous value: -"Établissements actifs (INSEE SIDE 2024), au plus."New value: +"Établissements actifs (INSEE SIDE 2024), au…"
    • changedInput schema / properties / etablissements_min / description
      Previous value: -"Établissements actifs (INSEE SIDE 2024), au moins."New value: +"Établissements actifs (INSEE SIDE 2024), au…"
    • changedInput schema / properties / prix_m2_min / description
      Previous value: -"Prix médian DVF au m² (€), au moins ; communes à…"New value: +"Prix médian DVF au m² (€), au moins ; communes…"
  3. First observed

TDQS

A3.6/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds the useful scope fact that filtering spans all of France, consistent with a closed dataset. It says nothing about pagination behaviour, result ordering defaults, or the volume of matches returned, even though the schema exposes curseur/decalage/limite.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Short and front-loaded: capability first, then the narrowing option, then the sibling routing hints. No filler. It loses a point for fragmentary, colon-chained syntax that reads more like notes than prose and takes a second pass to parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need no explanation, and annotations cover the safety profile. But for a 19-parameter filtering tool the description never addresses pagination or default ordering, and never mentions that procedure_en_cours only works with departement, which is a real usage trap. Adequate but with clear gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 74%, so the schema itself carries most parameter meaning and the baseline applies. The description does add a useful map of which indicator families the min/max filters cover (population, revenus, prix au m², établissements, vacance), but it leaves tri, ordre, limite, curseur, decalage, prix_m2_type, revenu_regle and the departement-dependent procedure_en_cours entirely to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a concrete resource (communes) and a concrete operation (filtering by socio-economic criteria across all of France), and enumerates the indicator families it can screen on (population, revenus, prix au m², établissements, vacance). It also explicitly separates itself from three named siblings, so an agent can route without opening schemas. The phrasing is telegraphic and lacks a clean verb at the start, which keeps it below a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit routing conditions: use departement to narrow, toise_comparer_zones to compare addresses, toise_maillage for institutional land ownership, toise_cannibalisation for network holes. That is real when-to-use-this-vs-alternative guidance. It does not say when this tool is the wrong choice (e.g., single-address lookups) or what to do with no filters at all.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources