Skip to main content
Glama

TOISE — intelligence foncière

Ce qu'une société possède en France

toise_patrimoine
Read-onlyIdempotent

Combien de foncier possède cette société ou ce groupe en France : total national de locaux et parcelles, par département et par commune. Par siren ou nom ; parcelles=true pour la liste paginée. Personnes morales ; filiales non incluses (toise_groupe, ou toise_owner_intelligence pour tout en un appel).

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

Input Schema

NameRequiredDescriptionDefault
nomNoDénomination, ou son début…
sirenNo
limiteNo
curseurNo
parcellesNoVrai : rend aussi la liste des parcelles…
code_inseeNo
departementNo

Output Schema

NameRequiredDescriptionDefault
liensNoLiens vers la fiche TOISE et vers des services de…
quotaNoQuota du jour après cet appel : { fonction, limite…
sourceYes
curseurNo
lectureNo
partielNotrue : une source n’a pas répondu, des champs manquent…
sourcesNoProvenance : nom, licence, millésime de chaque source.
has_moreNo
warningsYes
parcellesNoVide sauf parcelles=true.
perimetreYes
detenteursYes
par_communeNo
quota_unitesNoUnités d’usage du jour : consommees_par_cet_appel…
champs_absentsNoDonnées absentes du résultat partiel.
total_nationalYesComptes exacts du SIREN (locaux, communes, départements)…
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…
par_departementNo
total_parcellesNoNombre RÉEL de parcelles distinctes du SIREN…
parcelles_echantillonNoParcelles lues dans les 300 lignes sources…
total_parcelles_exactNo
agregats_sur_echantillonNoVrai : les répartitions portent sur un échantillon…

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / nom / description
      Previous value: -"Dénomination, ou son début (3 caractères minimum)."New value: +"Dénomination, ou son début…"
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the read-only, idempotent, non-destructive, open-world profile, so the description's added value is meaningful: it discloses that only legal entities are covered, that subsidiaries are excluded, and that a paginated parcel listing is opt-in. It does not discuss result volume, pagination limits, or what happens when both nom and siren are supplied.

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 sentences, front-loaded with the capability and followed by identification mode, output depth, and scope exclusions. Nothing is redundant, though the parenthetical alternative-tool note is compressed tightly enough to require a second read.

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?

An output schema exists, so return-value shape need not be restated, and the description covers coverage limits and pagination behaviour. The remaining gap is the ambiguity around which identifier is required (zero required parameters) and the undocumented limite/curseur controls for the paginated mode.

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 low (29%), yet the description only clarifies two of seven parameters: the siren-or-name identification path and the parcelles pagination flag. The departement/code_insee filters are merely implied by 'par département et par commune', and limite and curseur are left entirely undocumented in both the schema and the description.

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?

The description states a specific verb and resource ('Combien de foncier possède cette société ou ce groupe en France') and enumerates the granularity of the answer (total national, par département, par commune). It also explicitly delimits scope ('Personnes morales ; filiales non incluses'), which lets an agent separate it from toise_groupe and toise_owner_intelligence without opening any schema.

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 names the conditions that route away from this tool: consolidated subsidiaries go to toise_groupe, and a one-call everything answer goes to toise_owner_intelligence. It also indicates how to trigger the paginated parcel list (parcelles=true). It stops short of a full when/when-not statement (e.g. no guidance on when to prefer this over toise_droits_fonciers or toise_friches).

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