Skip to main content
Glama

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

Micro-foncier ou régime réel

micro_foncier_ou_reel
Read-onlyIdempotent

Pour des revenus de location vide (location nue) en France : calcule la base imposable au micro-foncier (abattement de 30 %, loyers bruts jusqu’à 15 000 €) et au régime réel (loyers − intérêts − charges déductibles), avec le déficit foncier imputable sur le revenu global (limite 10 700 €) ou reportable dix ans. Donne des bases, pas l’impôt, et ne choisit pas le régime. À utiliser pour « micro-foncier ou réel », « déficit foncier », « abattement 30 % ».

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": {
      "loyers": "<loyers>"
    },
    "name": "micro_foncier_ou_reel"
  }
}

Input Schema

NameRequiredDescriptionDefault
loyersYesLoyers bruts encaissés sur l’année, toutes locations vides du foyer, en euros.
chargesNoAutres charges déductibles de l’année (taxe foncière hors ordures ménagères, assurance, travaux d’entretien, charges non récupérables, frais de gestion), en euros.
interetsNoIntérêts d’emprunt et assurance emprunteur de l’année, en euros.

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 cover safety (readOnly, idempotent, closed-world), so the description's job is domain behavior — and it delivers: the 30% abattement, the €15,000 gross-rent ceiling, the deficit imputation cap of €10,700, and the ten-year carryforward. It also discloses that the return is a set of bases rather than an impôt, which is the key caveat a caller needs; only the exact return shape is left implicit.

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?

The scope is front-loaded in the opening clause, and the parenthetical figures are load-bearing thresholds rather than filler. The final sentence about what the tool does not do is well placed, though the description is dense enough that the usage triggers could have been folded in more tightly.

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 only three fully documented parameters, no output schema, and safety covered by annotations, the description supplies everything needed: applicable rules, the two regimes being compared, the deficit treatment, and the explicit limit that no tax is computed. Nothing essential is missing, though the shape of the returned bases is left to inference.

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 coverage is 100%, so the baseline is 3, but the description adds real meaning: 'loyers bruts jusqu'à 15 000 €' explains why the loyers parameter triggers the micro-foncier ceiling, and the enumerated deduction categories (intérêts, charges déductibles) map onto the interets and charges parameters. It doesn't add units or edge-case handling beyond what the schema already documents.

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 gives a specific verb and resource: it computes the taxable base ('base imposable') under both micro-foncier and régime réel for unfurnished French rental income. It scopes the domain to 'location nue' and explicitly disclaims two adjacent functions ('Donne des bases, pas l'impôt, et ne choisit pas le régime'), which cleanly separates it from tax-calculation or regime-selection siblings.

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?

Usage is anchored with explicit trigger phrases ('micro-foncier ou réel', 'déficit foncier', 'abattement 30 %'), so an agent can match user intent directly. It also states a boundary condition (no tax amount, no regime choice), but it never names a sibling to redirect to when the user actually wants a regime decision or an actual tax figure.

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