Skip to main content
Glama

TOISE — intelligence foncière

Bailleurs et gros détenteurs d'une commune

toise_bailleurs
Read-onlyIdempotent

Qui détient les murs d'une commune : les plus gros propriétaires personnes morales, bailleurs sociaux et collectivités écartés. Bailleurs sociaux et publics écartés par défaut (inclure_public). Paginé. Parcelles : toise_proprietaire.

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

Input Schema

NameRequiredDescriptionDefault
limiteNo
curseurNo
code_inseeYes
inclure_publicNoVrai : ne pas écarter les bailleurs…

Output Schema

NameRequiredDescriptionDefault
liensNoLiens vers la fiche TOISE et vers des services de…
notesNo
quotaNoQuota du jour après cet appel : { fonction, limite…
filtreYes{ publics_ecartes: bool, nb_publics_ecartes, motif }.
sourceYes
curseurYes
partielNotrue : une source n’a pas répondu, des champs manquent…
sourcesYes
affichesYes
has_moreYestrue : d'autres détenteurs existent au-delà de la liste…
warningsYes
bailleursYes
millesimeYesAnnée d'observation du fichier foncier, lue en base ; ou {…
code_inseeYes
parc_socialNoRPLS, SDES : logements locatifs sociaux de la commune…
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_ecartesNo5 premiers publics et sociaux écartés, avec catégorie…
total_detenteursYesNombre réel de personnes morales (SIREN distincts)…
absence_de_resultatNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / inclure_public / description
      Previous value: -"Vrai : ne pas écarter les bailleurs sociaux…"New value: +"Vrai : ne pas écarter les bailleurs…"
  2. Changed1 schema field changed
    • addedOutput schema / properties / parc_social
      Added value: +{
      +  "description": "RPLS, SDES : logements locatifs sociaux de la commune…",
      +  "type": "object"
      +}
  3. First observed

TDQS

B3.3/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=false, so the safety profile is fully covered. Beyond that, the description adds two genuinely useful behavioral facts: results are paginated ('Paginé'), and social/public landlords are filtered out by default. It does not say how the exclusion is applied or what happens at the end of pagination, so it adds context without reaching a 4.

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?

It is short and front-loaded with the scope, which is good. But the exclusion rule is stated twice ('bailleurs sociaux et collectivités écartés' then 'Bailleurs sociaux et publics écartés par défaut'), and the fragmented, clipped phrasing costs clarity without adding information.

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 pagination plus the default filter are covered. For a 4-parameter tool with 25% schema coverage and a non-obvious exclusion policy, the definition still leaves the required code_insee and the pagination mechanics implicit, making it adequate but not complete.

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 25%, so the description must carry weight. It does explain inclure_public's meaning and default (invert the exclusion filter), and 'Paginé' implicitly signals curseur/limite. But code_insee, limite and curseur are never explained in the description, leaving the required parameter and the page-size cap undocumented in prose — though defaults/maximums exist in the schema itself.

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 first clause names the resource precisely: the largest legal-entity property owners ('les plus gros propriétaires personnes morales') of a commune, with an explicit exclusion rule (social landlords and public bodies). It also routes to toise_proprietaire for parcel-level data, distinguishing itself from that sibling. The single-sentence telegraphic style slightly obscures the verb (list/rank), keeping it short of a 5.

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 implies the use case (finding who owns the walls of a commune at owner level) and names toise_proprietaire as the alternative for parcel-level queries, which is useful routing. However, there is no explicit when-to-use vs. when-not, and no statement of prerequisites or of what to do when the default filter has already removed the entities the user wants.

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