Skip to main content
Glama

TOISE — intelligence foncière

Indicateurs réglementaires d’une commune et QPV

toise_indicateurs_territoire
Read-onlyIdempotent

Une commune est-elle en zone tendue, Pinel (ABC), PTZ ou déficitaire SRU : indicateurs RÉGLEMENTAIRES officiels, pas socio-économiques. Aussi densité, URSSAF, QPV, SSMSI, fibre, PFAS, gares, tourisme, finances, climat DRIAS 2030-2100. Population, revenus, prix : toise_communes_cibles ou toise_comparer_zones.

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_indicateurs_territoire"
  }
}

Input Schema

NameRequiredDescriptionDefault
latNo
lonNo
adresseNo
code_inseeNo

Output Schema

NameRequiredDescriptionDefault
qpvYes{ dans_qpv, quartier { code, nom, commune, code_insee }…
sruYes{ disponible, soumise, taux_logements_sociaux_pct…
zanNoCerema : flux_annuels…
modeYes
liensNoLiens vers la fiche TOISE et vers des services de…
quotaNoQuota du jour après cet appel : { fonction, limite…
climatNoMétéo-France, données climatologiques mensuelles ouvertes…
emploiNoFrance Travail : tension…
curseurNo
densiteYes{ disponible, niveau (1 à 7), libelle, millesime, source…
partielNotrue : une source n’a pas répondu, des champs manquent…
sourcesYes
has_moreYes
warningsYes
millesimeNoMillésime de chaque indicateur (chaîne) ou { valeur:null…
code_inseeYes
programmesNo{ acv, pvd, ort } : { membre, date_convention, source…
zonage_abcYes{ disponible, valeur (A bis, A, B1, B2, C), millesime…
zonage_ptzYes{ disponible, valeur (1, 2, 3), zone_abc, millesime…
delinquanceNoSSMSI (faits enregistrés, dernière année) : indicateurs[{…
zone_tendueYes{ disponible, valeur:boolean, motif, millesime, source…
quota_unitesNoUnités d’usage du jour : consommees_par_cet_appel…
champs_absentsNoDonnées absentes du résultat partiel.
marche_travailNoFrance Travail Marché du travail : indicateurs {offres…
adresse_retenueNo
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…
donnees_ouvertesNoDonnées ouvertes de la commune (12/11/2026) : volets gares…
finances_localesNoComptes OFGL de la commune et de son EPCI : dette, épargne…
effectifs_salariesNoURSSAF (ODbL) : salariés privés et établissements…
commune_de_referenceNoCommune mère pour un arrondissement…
amenagements_cyclablesNoBNAC : km_total, km_protege, part_protege_pct, par_type…
indicateurs_indisponiblesNoIndicateurs dont le jeu officiel n’a pas répondu.
mobilites_professionnellesNoINSEE MOBPRO : actifs_residents, part_dans_la_commune_pct…

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / marche_travail
      Added value: +{
      +  "description": "France Travail Marché du travail : indicateurs {offres…",
      +  "type": "object"
      +}
  2. Changed2 schema fields changed
    • addedOutput schema / properties / amenagements_cyclables
      Added value: +{
      +  "description": "BNAC : km_total, km_protege, part_protege_pct, par_type…",
      +  "type": "object"
      +}
    • addedOutput schema / properties / mobilites_professionnelles
      Added value: +{
      +  "description": "INSEE MOBPRO : actifs_residents, part_dans_la_commune_pct…",
      +  "type": "object"
      +}
  3. Changed1 schema field changed
    • changedOutput schema / properties / climat / description
      Previous value: -"Météo-France DPClim, station la plus proche…"New value: +"Météo-France, données climatologiques mensuelles ouvertes…"
  4. Changed1 schema field changed
    • addedOutput schema / properties / climat
      Added value: +{
      +  "description": "Météo-France DPClim, station la plus proche…",
      +  "type": "object"
      +}
  5. Changed1 schema field changed
    • addedOutput schema / properties / delinquance
      Added value: +{
      +  "description": "SSMSI (faits enregistrés, dernière année) : indicateurs[{…",
      +  "type": "object"
      +}
  6. Changed1 schema field changed
    • changedOutput schema / properties / emploi / description
      Previous value: -"France Travail : tension, demandeurs, offres…"New value: +"France Travail : tension…"
  7. Changed5 schema fields changed
    • addedOutput schema / properties / donnees_ouvertes
      Added value: +{
      +  "description": "Données ouvertes de la commune (12/11/2026) : volets gares…",
      +  "type": "object"
      +}
    • addedOutput schema / properties / effectifs_salaries
      Added value: +{
      +  "description": "URSSAF (ODbL) : salariés privés et établissements…",
      +  "type": "object"
      +}
    • addedOutput schema / properties / finances_locales
      Added value: +{
      +  "description": "Comptes OFGL de la commune et de son EPCI : dette, épargne…",
      +  "type": "object"
      +}
    • addedOutput schema / properties / programmes
      Added value: +{
      +  "description": "{ acv, pvd, ort } : { membre, date_convention, source…",
      +  "type": "object"
      +}
    • addedOutput schema / properties / zan
      Added value: +{
      +  "description": "Cerema : flux_annuels…",
      +  "type": "object"
      +}
  8. Changed1 schema field changed
    • addedOutput schema / properties / emploi
      Added value: +{
      +  "description": "France Travail : tension, demandeurs, offres…",
      +  "type": "object"
      +}
  9. First observed

TDQS

B3.3/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=true, so the safety profile is covered. The description adds only the useful distinction that returned figures are official regulatory classifications rather than modelled socio-economic estimates. It says nothing about coverage limits, data vintage, or what happens when the commune is not in a zone.

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

Conciseness3/5

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

The leading clause front-loads the core regulatory question well, but the middle is an unstructured comma dump of ten unrelated indicator families. Each item is informative but the list has no grouping or priority, so the reader must parse it rather than scan it. The routing sentence at the end is tight and earns its place.

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-value explanation is rightly omitted, and the indicator scope is broadly sketched. However, for a tool with four optional parameters and none required, the description never establishes the minimum input needed to resolve a commune — the single most important thing an agent must know before calling it.

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

Parameters2/5

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

Schema description coverage is 0% across four parameters, and the description never mentions lat, lon, adresse or code_insee. It therefore leaves the agent with no explanation of how to identify the commune or whether the four locators are alternatives or must be combined. With zero schema documentation, this is a substantive gap rather than a minor one.

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 the resource concretely — official regulatory indicators for a commune (zone tendue, Pinel ABC, PTZ, SRU deficit) — and explicitly contrasts it with socio-economic data. The long secondary keyword list (densité, URSSAF, QPV, SSMSI, fibre, PFAS, gares...) makes the scope broad but recognizable. It stops short of a clean single-verb statement, reading more like a keyword catalogue than a definition.

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 an explicit negative scoping rule ('indicateurs RÉGLEMENTAIRES officiels, pas socio-économiques') and routes population/revenus/prix queries to toise_communes_cibles or toise_comparer_zones by name. What's missing is guidance versus topically adjacent siblings such as toise_zonage_commune or toise_contraintes, which an agent could plausibly confuse with this tool.

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