Skip to main content
Glama

TOISE — intelligence foncière

Les diagnostics énergétiques autour d’une parcelle

toise_dpe
Read-onlyIdempotent

Quels sont les diagnostics de performance énergétique (DPE) d'une adresse ou d'un quartier : étiquettes, consommation, surface, date, logements et tertiaire. Recherche par proximité (le DPE n'a pas de référence cadastrale) : un DPE listé peut être celui du voisin. Adresse, lat/lon, parcelle ou commune ; ADEME, depuis 2021.

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

Input Schema

NameRequiredDescriptionDefault
latNo
lonNo
depuisNoNe garder que les DPE établis depuis cette…
adresseNo
curseurNo
rayon_mNo
sectionNo
travauxNoBouquet : classe estimée après travaux…
code_inseeNo
numero_parcelleNo

Output Schema

NameRequiredDescriptionDefault
pageNo
liensNoLiens vers la fiche TOISE et vers des services de…
quotaNoQuota du jour après cet appel : { fonction, limite…
totalYesDiagnostics au total (tertiaire + logement) pour cette…
centreNoCentre de la recherche (lat, lon) ; null en recherche par…
entreeYesMode de recherche utilisé.
curseurYes
partielNotrue : une source n’a pas répondu, des champs manquent…
rayon_mYes
sourcesYes
has_moreYes
parcelleNoRéférences demandées…
warningsYes
retournesNoDiagnostics rendus dans cette page.
simulationNoAvec travaux : DPE de départ…
vide_motifNo
diagnosticsYes
quota_unitesNoUnités d’usage du jour : consommees_par_cet_appel…
indisponiblesNoJeux ADEME sans réponse : la liste et les totaux sont alors…
total_par_jeuNoTotal réel par jeu ADEME interrogé (tertiaire, logement).
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…

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / depuis / description
      Previous value: -"Ne garder que les DPE établis depuis cette année…"New value: +"Ne garder que les DPE établis depuis cette…"
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the description's added value is the substantive caveat that DPEs carry no cadastral reference and a returned record may belong to a neighbouring building, plus the ADEME source and the 2021-onward coverage window. It does not mention pagination despite a curseur parameter, which keeps it below 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.

Conciseness4/5

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

Three tight sentences, front-loaded with the returned fields, then the critical proximity caveat, then the accepted inputs and provenance. Dense but every clause carries information; only the trailing source/date fragment feels compressed to the point of terseness.

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?

The description is adequate for a lookup tool and the output schema handles return-value explanation, but for a 10-parameter tool with 20% schema coverage it leaves real gaps: no default or maximum radius behaviour, no pagination hint for curseur, and no explanation of the travaux scenario. An agent could still call it, but would be guessing on several knobs.

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?

With only 20% schema description coverage across 10 parameters, the description does useful work by mapping the four locator strategies onto adresse, lat/lon, section+numero_parcelle and code_insee. However the remaining parameters — rayon_m including its 20–300 m bounds, depuis, curseur and especially the travaux works-bundle enum array — receive no semantic explanation in either place.

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 names the resource precisely (DPE — diagnostics de performance énergétique) and states both the geographic scope (an address or a neighbourhood) and what each record exposes: energy labels, consumption, surface area, date, residential and tertiary. An agent can tell this is an energy-diagnostics lookup and not a parcel or transaction tool without opening the 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 gives clear entry conditions by enumerating the accepted locators (adresse, lat/lon, parcelle, commune) and explains why a proximity search is used. It does not name a sibling alternative or state when this tool should be avoided, so it falls short of full when/when-not routing.

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