Skip to main content
Glama
Sign In

Marcel

by fr.marcel-retraite
OverviewDiscussionsAdmin

Calculer une plus-value immobilière des particuliers

simulate_pv_immo_ir
Read-onlyIdempotent

Calcule la plus-value immobilière imposable à l'impôt sur le revenu (particulier ou SCI à l'IR) : abattements pour durée de détention (CGI art. 150 VC), exonération de la résidence principale, frais d'acquisition au forfait de 7,5 %. Entrées : prix d'achat, prix de vente, durée, nature du bien, frais. Sortie : plus-value brute, abattements, impôt et prélèvements sociaux. Calcul non couvert par les jeux de référence Marcel : résultat indicatif.

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": {
      "prixAcquisition": "<prixAcquisition>",
      "prixCession": "<prixCession>",
      "anneesDetention": "<anneesDetention>"
    },
    "name": "simulate_pv_immo_ir"
  }
}

Input Schema

NameRequiredDescriptionDefault
prixCessionYesPrix de vente en euros
anneesDetentionYesDurée de détention en années entières
prixAcquisitionYesPrix d'achat du bien en euros
travauxNonDeduitsNoTravaux majorant le prix d'acquisition
residencePrincipaleNoRésidence principale — exonération totale si true
fraisAcquisitionReelsNoFrais réels si connus (sinon forfait 7,5%)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds genuine context beyond that: the exact output components (plus-value brute, abattements, impôt, prélèvements sociaux) and the caveat that the figure is indicative and outside the reference datasets.

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?

Three compact sentences plus explicit Entrées/Sortie labelling, with the legal basis and the indicative-result caveat both front-loaded. No redundant restatement of the tool name.

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 no output schema, the description correctly compensates by enumerating the returned values. The scope and legal mechanics are adequately covered; only edge handling (e.g. fractional détention, multi-owner splits) is left unstated.

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 coverage is 100% and every parameter is described in the schema, so the baseline is 3. The description only restates the input list and the 7,5% forfait default that the schema already documents for fraisAcquisitionReels; it adds no rules such as how travauxNonDeduits interacts with the forfait.

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) and precise resource (plus-value immobilière imposable à l'IR) and bounds the population (particulier ou SCI à l'IR). It also distinguishes itself from the validated Marcel reference sets, which is exactly the differentiator an agent needs among the many simulate_* 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?

Scope is clear: French residents / SCI à l'IR, with the legal basis (CGI art. 150 VC) and the résidence principale exoneration case called out. The note that the result is not covered by the Marcel reference sets implicitly tells the agent not to expect validate_results to confirm it, though no sibling alternative is named explicitly.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Marcel toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources