Skip to main content
Glama

Zéro problème : calculs du bailleur en France

Date d’interdiction de louer (DPE)

interdiction_location_dpe
Read-onlyIdempotent

Donne la date à partir de laquelle un logement classé G, F ou E selon le DPE ne peut plus être loué en France métropolitaine (G depuis le 1er janvier 2025, F au 1er janvier 2028, E au 1er janvier 2034), et pour un bail en cours la première échéance concernée selon le type de bail. À utiliser pour « DPE G location interdite quand », « passoire thermique bail en cours ».

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": {
      "classe": "<classe>"
    },
    "name": "interdiction_location_dpe"
  }
}

Input Schema

NameRequiredDescriptionDefault
classeYesClasse énergie indiquée sur le DPE (A à G).
type_bailNovide = location nue (3 ans) ; videPm = location nue, bailleur société (6 ans) ; meuble = meublé (1 an) ; etudiant = meublé étudiant (9 mois). Par défaut : vide.
date_effetNoDate de prise d’effet du bail en cours, AAAA-MM-JJ. Absente : date pour un nouveau bail.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare a read-only, idempotent, closed-world lookup, and the description adds the substantive domain rule the agent needs: fixed cut-off dates per class and the notion of « première échéance concernée » for an ongoing lease. It does not say what is returned for classes A–D (presumably no restriction) nor the exact response shape, 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?

A single dense sentence, front-loaded with the answer and followed by the per-class dates and the ongoing-lease clause, then the trigger phrasings. Every clause carries information, though the parenthetical date list makes it long enough to be worth tightening.

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?

For a deterministic, three-parameter lookup with no output schema, the definition explains the computation rule, the lease-type dependency and the default for date_effet. Only the outcome for classes A–D and the response format are left implicit, which is a minor gap for an agent that can infer it.

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 100%, so classe, type_bail and date_effet are already fully documented with enums and defaults. The description reinforces the lease-in-progress case and the lease-type dependency but adds no format or edge-case detail (e.g. behavior for A–D) beyond what the schema states, so baseline 3 is appropriate.

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?

Names a precise resource and output: the date from which a G/F/E-class dwelling can no longer be rented in metropolitan France, with the concrete dates spelled out per class. That specificity, plus the lease-in-progress clause, clearly separates it from the sibling tools (notary fees, rent revision, capital gains).

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?

Provides explicit trigger phrasings (« DPE G location interdite quand », « passoire thermique bail en cours ») that tell the agent exactly what user question this tool answers. It stops short of naming alternatives or stating when not to use it, but the sibling set covers unrelated topics so the risk of misrouting is low.

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