Skip to main content
Glama

TOISE — intelligence foncière

Implantation d’un commerce : offre, enseignes absentes, habitants

toise_implantation
Read-onlyIdempotent

Quelle enseigne manque autour de ce point : concurrence et demande par catégorie de commerce dans la zone de chalandise. Catégorie obligatoire (voir l'enum). Aussi salariés URSSAF et indice de fréquentation. Source OpenStreetMap : si SOURCE_INDISPONIBLE, une relance au plus, puis toise_etablissements_naf.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "mode": "<mode>",
      "categorie": "<categorie>"
    },
    "name": "toise_implantation"
  }
}

Input Schema

NameRequiredDescriptionDefault
kmNoRayon en km, de 1 à 30 (rayon, isodistance).
latNo
lonNo
modeYesvoiture, velo, poids_lourd : jusqu’à 45 min…
limiteNo
traficNoAjouter le trafic routier…
adresseNo
curseurNo
minutesNoDurée du trajet, de 5 à 45 (voiture) ou 30…
decalageNo
enseigneNoEnseigne visée (ex.
categorieYesCatégorie de commerce étudiée.
transportsNoAjouter les arrêts de transport en commun…

Output Schema

NameRequiredDescriptionDefault
okYes
dateNo
liensNoLiens vers la fiche TOISE et vers des services de…
offreYesTotal de commerces (minimum), sans enseigne connue, densité…
quotaNoQuota du jour après cet appel : { fonction, limite…
actifsNoSalariés privés URSSAF au 31/12/2025 des communes touchées…
departYes
emploiNoFrance Travail (La Bonne Boîte) : employeurs du secteur à…
traficNoTrafic routier (TMJA, sources ouvertes) : tronçons de la…
curseurNo
demandeNoHabitants estimés de la zone, surface, communes…
partielNotrue : une source n’a pas répondu, des champs manquent…
sourcesYes
cyclableNoBNAC autour du départ : km_500m, km_1km, km protégés, piste…
enseigneNoEnseigne visée : magasins dans la zone, à moins de 30 km…
has_moreYesVrai si la liste a d’autres éléments : rappeler avec…
lecturesYes
warningsYesAvertissements (paramètres ignorés, données partielles).
categorieYesClé et intitulé de la catégorie.
perimetreYesMode et intitulé de la zone (sans la géométrie).
transportsNoArrêts de transport en commun (transport.data.gouv.fr)…
explicationNoDistance à vol d’oiseau vs temps de trajet : pourquoi un…
flux_pietonsNoFlux piéton RECONSTRUIT (estimation, non mesurée) au point…
quota_unitesNoUnités d’usage du jour : consommees_par_cet_appel…
frequentationNoIndice relatif 0-100…
champs_absentsNoDonnées absentes du résultat partiel.
liste_tronqueeNoVrai si la page ne contient pas tous les commerces de la…
sources_detailNo
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…

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / transports / description
      Previous value: -"Ajouter les arrêts de transport en commun dans…"New value: +"Ajouter les arrêts de transport en commun…"
  2. Changed2 schema fields changed
    • addedOutput schema / properties / cyclable
      Added value: +{
      +  "description": "BNAC autour du départ : km_500m, km_1km, km protégés, piste…",
      +  "type": "object"
      +}
    • addedOutput schema / properties / flux_pietons
      Added value: +{
      +  "description": "Flux piéton RECONSTRUIT (estimation, non mesurée) au point…",
      +  "type": [
      +    "object",
      +    "null"
      +  ]
      +}
  3. Changed3 schema fields changed
    • changedInput schema / properties / transports / description
      Previous value: -"Ajouter les arrêts de transport en commun dans la…"New value: +"Ajouter les arrêts de transport en commun dans…"
    • addedOutput schema / properties / actifs
      Added value: +{
      +  "description": "Salariés privés URSSAF au 31/12/2025 des communes touchées…",
      +  "type": [
      +    "object",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / frequentation
      Added value: +{
      +  "description": "Indice relatif 0-100…",
      +  "type": [
      +    "object",
      +    "null"
      +  ]
      +}
  4. Changed1 schema field changed
    • addedOutput schema / properties / emploi
      Added value: +{
      +  "description": "France Travail (La Bonne Boîte) : employeurs du secteur à…",
      +  "type": "object"
      +}
  5. First observed

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavior: the OSM data source, the SOURCE_INDISPONIBLE error state with a one-retry policy, and the secondary URSSAF/footfall inputs. Beyond that it says nothing about the cost of the call, geographic coverage limits, or how the zone is computed, so the added disclosure is real but thin against a 13-parameter tool.

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?

Three dense sentences that front-load the core question before the mandatory-parameter note and the source/fallback clause. Little is wasted, though the sentence about URSSAF payroll and footfall is telegraphic and the fallback clause is packed into the same breath as the data source.

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?

The output schema exists, so return values need not be explained, and annotations cover the safety profile. What is missing for a 13-parameter geo-analysis tool is any explanation of how the catchment zone is defined (km radius vs isodistance vs drive time) and what the cursor/pagination and traffic/transports flags actually do. Enough to get a first call right, not enough to call it well.

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 coverage is only 54% across 13 parameters, so the description needs to compensate for parameters like curseur, decalage, limite, adresse and enseigne, which are undocumented in both places. Instead it only repeats that catégorie is mandatory and points to the enum, information the schema already carries via required/enum. Some schema descriptions are visibly truncated (mode, enseigne), and the description does not fill those gaps, so the agent still cannot infer how km, mode and minutes interact.

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 states a specific analytical question (which retail brand/category is missing around a point) plus the resources involved: competition, demand per category in the catchment area, URSSAF payroll data and a footfall index. It is clearly distinguishable from generic siblings like toise_etude_marche because it names the missing-enseigne angle and the OSM source. It stops short of a crisp verb+resource formulation, reading more as a question 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?

Gives an explicit routing rule for a failure condition: if the source returns SOURCE_INDISPONIBLE, retry once, then fall back to toise_etablissements_naf. It also states that catégorie is a prerequisite. It does not say when to prefer this over the other market-analysis siblings, so no exclusions are offered.

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