Skip to main content
Glama

TOISE — intelligence foncière

Balayer un département ou classer les détenteurs d’une commune

toise_maillage
Read-onlyIdempotent

Où mailler un territoire : communes d'un département classées par population, parcelles et propriétaires personnes morales. Par departement. Filtrer toute la France sur revenu, prix ou vacance : toise_communes_cibles.

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

Input Schema

NameRequiredDescriptionDefault
limiteNo
curseurNo
decalageNo
code_inseeNo
departementNo
inclure_publicNoDétenteurs d’une commune : inclure…
population_maxNoBalayage : population maximale ; omettre…
population_minNoBalayage : population minimale d’une…

Output Schema

NameRequiredDescriptionDefault
modeYes
liensNoLiens vers la fiche TOISE et vers des services de…
quotaNoQuota du jour après cet appel : { fonction, limite…
totalNoBalayage : communes correspondant à la fourchette, AVANT…
filtreNo
lacuneNoBalayage : département absent du fichier foncier, avec…
limiteNo
curseurYes
lectureNo
partielNotrue : une source n’a pas répondu, des champs manquent…
publicsNoDétenteurs : aperçu (5 au plus) des publics écartés.
sourcesYes
communesNo
decalageNo
has_moreYes
retenuesNoBalayage : identique à total…
warningsYes
renvoyeesNoBalayage : communes rendues dans cette page.
code_inseeNo
detenteursNoDétenteurs : personnes morales classées par nombre de…
motif_videNoMotif quand la liste est vide.
departementNo
quota_unitesNoUnités d’usage du jour : consommees_par_cet_appel…
champs_absentsNoDonnées absentes du résultat partiel.
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…
publics_ecartesNoDétenteurs : bailleurs sociaux et collectivités écartés.
sans_populationNoBalayage : communes sans population rendue par le…
communes_du_departementNoBalayage : communes du département.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / inclure_public / description
      Previous value: -"Détenteurs d’une commune : inclure bailleurs…"New value: +"Détenteurs d’une commune : inclure…"
    • changedInput schema / properties / population_max / description
      Previous value: -"Balayage : population maximale ; omettre pour…"New value: +"Balayage : population maximale ; omettre…"
    • changedInput schema / properties / population_min / description
      Previous value: -"Balayage : population minimale d’une commune…"New value: +"Balayage : population minimale d’une…"
  2. Changed1 schema field changed
    • changedInput schema / properties / population_max / description
      Previous value: -"Balayage : population maximale ; omettre pour ne…"New value: +"Balayage : population maximale ; omettre pour…"
  3. 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, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered by structured data. The description's only added behavioral content is the shape of what comes back (communes ranked by population, parcels, owners). It says nothing about pagination behavior despite limite/curseur/decalage, nor about limits on result volume.

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 text is short and front-loads the core purpose, which is good. But it is telegraphic and fragmented ('Par departement.' is a standalone sentence that adds little), and the second mode plus the sibling pointer are crammed into the same run-on line, making the mode switch harder to parse than it needs to be.

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 values need not be described, and annotations cover the read-only contract. Still, for an 8-parameter dual-mode tool with zero required parameters, the definition does not explain how to select a mode, what happens when both identity parameters are given, or how paging works. That is a meaningful gap for correct invocation.

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 only 38%, so the description is expected to compensate. It does partially: 'communes d'un département' and 'détenteurs d'une commune' implicitly tie the two operating modes to the departement and code_insee parameters, which the schema does not explain. However, limite, curseur and decalage remain undocumented in both places, leaving the pagination contract opaque.

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 uses a concrete verb-plus-resource framing ('Où mailler un territoire'), then enumerates both modes: ranking a département's communes by population/parcels/legal-entity owners, and classifying the détenteurs of a commune. It also names the sibling it is not (toise_communes_cibles), so an agent can separate the two. It falls short of 5 because the second mode is only hinted at ('propriétaires personnes morales') rather than stated as a distinct operation.

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 routing rule: for France-wide filtering on revenu, prix or vacance, use toise_communes_cibles instead. That is a real alternative-with-condition, not just a mention. It stops short of 5 because it never states when this tool should NOT be used within its own two modes (e.g. what to do when a commune code and a département are both supplied).

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