Skip to main content
Glama

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

Révision du loyer (IRL)

revision_loyer_irl
Read-onlyIdempotent

Calcule le nouveau loyer mensuel hors charges après révision annuelle selon l’indice de référence des loyers (IRL, INSEE) pour un bail d’habitation en France : nouveau loyer = loyer × IRL du trimestre / IRL du même trimestre un an plus tôt (art. 17-1 de la loi du 6 juillet 1989). Indique aussi le blocage de la révision pour un logement classé F ou G. À utiliser pour « de combien puis-je augmenter mon loyer », « révision IRL », « indexation du loyer ».

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": {
      "loyer": "<loyer>"
    },
    "name": "revision_loyer_irl"
  }
}

Input Schema

NameRequiredDescriptionDefault
loyerYesLoyer mensuel actuel hors charges, en euros.
trimestreNoTrimestre de l’IRL prévu au bail, format AAAA-Tn (ex. 2026-T2). Par défaut : le dernier publié.
classe_dpeNoClasse énergie du logement (A à G), si connue. F et G : révision interdite pour les baux conclus ou reconduits depuis le 24 août 2022.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/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, closed-world), and the description adds genuine behavioral context beyond them: the computation method, the legal grounding, and a conditional rule that the result includes a revision freeze for F/G housing since 24 August 2022. It stops short of describing the return payload's fields or how the freeze is reported alongside the computed figure.

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?

Front-loads the computation and formula, then the DPE caveat, then the trigger phrases — a logical order with no filler. It is a dense single block, so a slightly more scannable structure would help, but every sentence carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter read-only calculation with no output schema, the description supplies the formula, the legal rule, the default-trimestre behavior implied by the schema, and the DPE-driven exception. An agent has everything needed to decide to call it and to interpret the two results it produces.

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 all three parameters are already documented, including the enum for trimestre and the DPE classes. The description reinforces the semantics of trimestre by explaining it is used as numerator and as the year-earlier denominator, but adds little beyond what the schema states, so the baseline of 3 applies.

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?

States a specific verb and resource (calculates the new monthly rent excluding charges after annual revision) and spells out the exact formula and legal basis (art. 17-1, loi du 6 juillet 1989). It also declares the secondary output (rent freeze for F/G-rated housing), which makes it unmistakable next to siblings like loyer_non_revise or interdiction_location_dpe.

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?

Gives explicit trigger phrasing ("de combien puis-je augmenter mon loyer", "révision IRL", "indexation du loyer"), which clearly frames the use case. It does not state when not to use it or name an alternative for the non-revised rent case, so exclusions are absent.

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