Skip to main content
Glama

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

Loyer non révisé : montant perdu et date limite

loyer_non_revise
Read-onlyIdempotent

Pour un bail d’habitation en France dont le loyer n’a pas été révisé selon l’IRL : calcule ce qui est déjà perdu (la révision ne joue qu’à partir de la demande, sans effet rétroactif) et la date jusqu’à laquelle la révision de l’année peut encore être demandée (un an après la date anniversaire, art. 17-1 de la loi du 6 juillet 1989). À utiliser pour « j’ai oublié de réviser le loyer », « révision loyer rétroactive », « augmentation loyer oubliée ».

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>",
      "date_depuis": "<date_depuis>"
    },
    "name": "loyer_non_revise"
  }
}

Input Schema

NameRequiredDescriptionDefault
loyerYesLoyer mensuel actuel hors charges, en euros.
trimestreNoTrimestre de l’IRL prévu au bail, format AAAA-Tn. Par défaut : le dernier publié.
date_depuisYesDate de la dernière révision ou du début du bail, AAAA-MM-JJ.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so safety is covered. The description adds genuinely useful behavioral context — non-retroactivity of the revision and the one-year window under art. 17-1 — but says nothing about the shape or units of the returned values, which matters for a calculation tool with no output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

Two dense sentences that front-load the scope, then the legal mechanic, then a compact set of retrieval phrases. No filler or repetition of the schema.

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?

Covers scope, legal rule and computation outputs for a three-parameter read-only calculator. It leaves the return structure unstated, which is acceptable given the explicit statement of what gets computed, though a hint about the result fields would close the gap.

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 the parameters (monthly rent excluding charges, IRL quarter with default described, last-revision date) are already fully documented. The description adds only indirect meaning, linking the one-year deadline to the anniversary/revision date parameter. Baseline 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 (calcule) plus the two concrete outputs — already-lost amount and the deadline for the yearly revision — scoped to a French residential lease whose rent has not been revised. The 'loyer non révisé' framing distinguishes it from the regular IRL revision sibling without needing 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?

Gives explicit trigger phrasings ('j'ai oublié de réviser le loyer', 'révision loyer rétroactive', 'augmentation loyer oubliée') that map user intent to this tool. It does not name the alternative tool for a regular, on-time revision, so the exclusions are implied rather than stated.

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