Skip to main content
Glama

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

Frais de notaire par département

frais_de_notaire
Read-onlyIdempotent

Pour un achat immobilier en France : calcule les « frais de notaire » détaillés — droits de mutation au taux du département (tableau DGFiP au 1er juin 2026, 5,00 % ou 4,50 % selon le département et le premier achat de résidence principale ; 0,715 % pour le neuf soumis à la TVA), émoluments du notaire selon le barème réglementé, contribution de sécurité immobilière et débours estimés. À utiliser pour « frais de notaire », « droits de mutation », « DMTO », « frais d’acquisition ».

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": {
      "prix": "<prix>",
      "departement": "<departement>"
    },
    "name": "frais_de_notaire"
  }
}

Input Schema

NameRequiredDescriptionDefault
neufNotrue si le bien est neuf et vendu avec TVA (VEFA, ou moins de 5 ans vendu par un professionnel).
prixYesPrix du bien indiqué dans l’acte, en euros, sans mobilier ni frais d’agence payés en plus par l’acheteur.
departementYesCode du département du bien : « 01 » à « 95 », « 2A », « 2B », « 971 » à « 974 », « 976 ».
primo_accedantNotrue si l’acheteur n’a pas été propriétaire de sa résidence principale dans les deux ans avant l’achat et que le bien deviendra sa résidence principale.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: the rate table source and vintage (DGFiP au 1er juin 2026), the 5,00 % vs 4,50 % split by department and first-time-buyer status, and the 0,715 % regime for VAT-liable new builds. It does not describe the shape of the returned breakdown, which is the only notable omission.

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?

Two sentences, front-loaded with the action and output, followed by the routing keywords. It is dense and somewhat long-winded with nested parentheses, but every clause carries rate logic or disambiguation value, so nothing is decorative.

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?

With 4 parameters, no output schema and full annotation coverage, the description does enough: it covers the computed components, the rate rules and the input conditions. The one thing an agent might still want is a hint about the response structure (totals vs itemized lines), which the phrase "détaillés" only implies.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100 %, so baseline would be 3. The description goes beyond it by explaining how the parameters interact: the department drives the DMTO rate, primo_accedant conditions the reduced rate, and neuf switches to the 0,715 % VAT regime. That causal mapping is not present in the schema text and materially helps correct invocation.

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 opens with a specific verb and resource ("calcule les « frais de notaire » détaillés") and enumerates the four cost components actually computed (droits de mutation, émoluments, contribution de sécurité immobilière, débours). An agent can immediately distinguish this from the sibling tools, which cover DPE, rent revision, LMNP and capital gains rather than acquisition costs.

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 supplies explicit trigger vocabulary ("frais de notaire", "droits de mutation", "DMTO", "frais d’acquisition"), which tells the agent when to route here. It gives no exclusions or named alternatives, but the sibling set is clearly non-overlapping, so the missing "when not to use" is a minor gap rather than a hazard.

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