Skip to main content
Glama

TOISE — intelligence foncière

Mission expansion : cibler, tracer, comparer — sans classement fusionné

toise_expansion
Read-only

Où ouvrir plusieurs sites dans un département (mission expansion) : communes cibles, zones de chalandise, implantation, comparaison et cannibalisation enchaînées. Résultats par section, sans classement unique fusionné.

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": {
      "territoire": "<territoire>"
    },
    "name": "toise_expansion"
  }
}

Input Schema

NameRequiredDescriptionDefault
detailNoDéfaut false : sortie résumée…
categorieNoCatégorie de commerce visée (voir l'enum).
territoireYesDépartement…
limite_communesNoCommunes candidates retenues de…
points_de_venteNo2 à 10 points de vente déjà ouverts…

Output Schema

NameRequiredDescriptionDefault
liensNoLiens vers la fiche TOISE et vers des services de…
quotaNoQuota du jour après cet appel : { fonction, limite…
partielNotrue : une source n’a pas répondu, des champs manquent…
sourcesNoProvenance : nom, licence, millésime de chaque source.
warningsYes
categorieNo
territoireYes
detail_omisNoBlocs omis du résumé…
interrompueNoVrai si une étape a arrêté la mission (compte ou quota)…
quota_unitesNoUnités d’usage du jour : consommees_par_cet_appel…
implantationsYesUne entrée par commune retenue, seulement si categorie est…
champs_absentsNoDonnées absentes du résultat partiel.
cannibalisationNoRésultat de toise_cannibalisation, seulement si…
communes_ciblesYesRésultat de toise_communes_cibles…
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…
zones_chalandiseYesUne entrée par commune retenue : résultat de…
classement_uniqueYesToujours null : voir motif_classement_unique.
comparaison_zonesNoRésultat de toise_comparer_zones sur les zones valides…
motif_classement_uniqueYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds real value by disclosing the output shape ('Résultats par section, sans classement unique fusionné') and that the steps run chained, warning the agent not to expect a single ranked list. It says nothing about cost/latency of a multi-step pipeline or about how many candidate locations are returned, which matters for a composite call.

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?

Two tight sentences, front-loaded with the decision question ('Où ouvrir plusieurs sites…') followed by the enumerated chain and the output caveat. Minor waste in the parenthetical '(mission expansion)' which restates the tool title.

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

Completeness4/5

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

For a 5-parameter composite with full schema coverage and an output schema, the description covers what it does, the ordered sections, and the non-fused output. The main remaining gap is the absence of any expectation-setting about execution cost or how the sectioned results relate to the individual sibling tools.

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 description coverage is 100%, so the enum, bounds and per-mode semantics of points_de_vente are already documented in the schema. The description only echoes the required 'département' scope and the multi-site nature of points_de_vente; it adds no meaning beyond the schema. Baseline 3 applies.

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 outcome (where to open several sites within a département) and enumerates the chained steps: communes cibles, zones de chalandise, implantation, comparaison, cannibalisation. This makes it legible as a composite/orchestration tool rather than a single analysis. It stops short of explicitly differentiating itself from the sibling analyses it chains (e.g. toise_cannibalisation, toise_implantation).

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

Usage Guidelines3/5

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

Use is implied by 'Où ouvrir plusieurs sites dans un département (mission expansion)', which signals a multi-site scouting scenario, and 'plusieurs sites' implicitly contrasts with single-site tools. However, there is no explicit when-not guidance and no named alternative for agents who only need one of the chained steps.

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