Skip to main content
Glama

TOISE — intelligence foncière

Contraintes et servitudes autour d’un lieu

toise_contraintes
Read-onlyIdempotent

Qu'est-ce qui peut bloquer ou renchérir un projet autour d'une adresse : servitudes, emplacements réservés, ABF et monuments historiques, prescriptions du PLU. Rayon 50 à 1 000 m (100 par défaut) : PLU, SUP, ABF, EBC, OAP, ZAC/PUP mentionnées. Inclut les risques Géorisques (PPRI/PPRT, radon, ICPE, argiles) : toise_risques seulement pour le détail communal. Non opposable.

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

Input Schema

NameRequiredDescriptionDefault
latNo
lonNo
limiteNo
niveauNoNe rendre que ce niveau de gravité.
adresseNo
curseurNo
rayon_mNo
code_inseeNo

Output Schema

NameRequiredDescriptionDefault
abfNoBloc architecte des Bâtiments de France : concerne {valeur…
modeYes
liensNoLiens vers la fiche TOISE et vers des services de…
pointNo{ lat, lon } centre du disque de lecture.
quotaNoQuota du jour après cet appel : { fonction, limite…
totalYesNombre réel de contraintes correspondant aux filtres, avant…
argilesNoNiveau maximal lu sur la grille 3×3 du disque…
comptesNoComptes RÉELS avant pagination : par niveau…
curseurYes
partielNotrue : une source n’a pas répondu, des champs manquent…
rayon_mNo
sourcesYes
verdictNoniveau (bloquant, chiffrable, ordinaire, indetermine) et…
has_moreYes
littoralNo{ commune_littorale, regime } ou { valeur:null, motif }.
warningsYes
code_inseeNo
retourneesNo
contraintesYes
quota_unitesNoUnités d’usage du jour : consommees_par_cet_appel…
non_opposableYesMention : non opposable sans lecture du règlement.
champs_absentsNoDonnées absentes du résultat partiel.
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…
document_durbanismeNoDocument d’urbanisme lu au Géoportail : nom, type…
contraintes_a_integrerYesTOUTES les contraintes lues…
couverture_contraintesYeslot3…

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds useful non-obvious context: the full upstream data sources it aggregates (PLU, SUP, ABF, EBC, OAP, ZAC/PUP, Géorisques), the radius default of 100 m, and the legal caveat "Non opposable" — a real behavioral qualifier an agent should not overlook. It does not explain pagination even though a curseur parameter exists.

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, front-loaded sentences: purpose first, then coverage and radius, then sibling routing and the legal caveat. Every clause carries information, though the acronym stacking (SUP, EBC, OAP, ZAC/PUP, PPRI/PPRT, ICPE) makes it heavy for readers unfamiliar with French planning jargon.

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 description is not required, and the annotations cover safety semantics. The gap is on the input side: eight largely undocumented optional parameters and no statement of which locator form is required or how cursor pagination works leaves the definition thin for a tool of this complexity.

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 only 13%, so the description must compensate, and it only partly does: it supplies the radius range and its 100 m default (the schema has no default). Nothing explains adresse, lat/lon, code_insee, curseur, or how these alternate locators combine — with all 8 parameters optional, the description leaves the agent guessing what minimally constitutes a valid call.

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 opens with a concrete framing ("Qu'est-ce qui peut bloquer ou renchérir un projet autour d'une adresse") and then enumerates the exact resource types returned: servitudes, emplacements réservés, ABF/monuments historiques, prescriptions du PLU, plus Géorisques risks. It partially differentiates from siblings by scoping toise_risques to commune-level detail only, but the boundary against other address-level siblings (e.g. toise_dossier_adresse) is not drawn.

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?

It states one explicit routing rule — use toise_risques for commune-level risk detail instead of this tool — which is genuine when-not guidance. However, there is no guidance on when to reach for this tool overall, and no indication of how the alternative addressing modes (adresse vs lat/lon vs code_insee) should be chosen.

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