Skip to main content
Glama

TOISE — intelligence foncière

Zones du PLU d'une commune

toise_zonage_commune
Read-onlyIdempotent

Quelles sont les zones du PLU d'une commune entière (U, AU, A, N) et où trouver leur règlement. Liste paginée, filtre type_zone. Règles d'une parcelle : toise_urbanisme. Ne rend ni règlement ni servitudes.

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": {
      "code_insee": "<code_insee>"
    },
    "name": "toise_zonage_commune"
  }
}

Input Schema

NameRequiredDescriptionDefault
limiteNo
curseurNo
type_zoneNoNe garder que ce type de zone.
code_inseeYes

Output Schema

NameRequiredDescriptionDefault
noteNoRepli d'arrondissement, le cas échéant.
liensNoLiens vers la fiche TOISE et vers des services de…
quotaNoQuota du jour après cet appel : { fonction, limite…
totalYesNombre réel de zones distinctes (après filtre `type_zone`)…
zonesYes
sourceYes
curseurYes
partielNotrue : une source n’a pas répondu, des champs manquent…
sourcesYes
affichesYes
decalageNo
has_moreYes
warningsYes
millesimeNo{ valeur:null, motif } en lecture directe…
code_inseeYes
quota_unitesNoUnités d’usage du jour : consommees_par_cet_appel…
champs_absentsNoDonnées absentes du résultat partiel.
code_interrogeYesCode de la commune qui porte le document…
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…
nb_polygones_totalNoNombre de polygones du document, toutes zones…
absence_de_resultatNoPrésent si total = 0 : cause et lecture.
procedure_urbanismeNoDocurba : { disponible, procedure_en_cours, procedure {…
document_intercommunalNoPLUi : { partition (DU_<siren>), document } ; les zones…

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/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 new behavior: the result is paginated, filtered by type_zone, and deliberately excludes règlement and servitudes. It stops short of stating result-set size or cursor semantics, so not a 5.

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

Conciseness5/5

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

Front-loaded with purpose, then filter, then the alternative, then the negative scope in a short fragment. No filler sentences; every clause carries routing or scoping information.

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?

With an output schema present, return structure needn't be described, and for a 4-parameter paginated lookup the description covers scope, filtering, and alternatives. The only material omission is pagination mechanics (cursor usage), a minor gap.

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

Parameters4/5

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

Schema coverage is only 25%, so the description must compensate, and it does: it names the type_zone filter and pagination (liste paginée), and frames code_insee as commune-wide scope. It does not explain how curseur is used or the limite default, so the compensation is partial.

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

Purpose5/5

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

States a specific resource (PLU zones U, AU, A, N of an entire commune) with an explicit scope ('commune entière') and distinguishes itself from the parcel-level sibling by naming toise_urbanisme.

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

Usage Guidelines5/5

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

Explicitly routes the agent: plot-level rules go to toise_urbanisme, and the description states what this tool will NOT return (règlement, servitudes), so the boundary against toise_reglement_plu is inferable from the negative scope.

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