Skip to main content
Glama
Sign In

Marcel

by fr.marcel-retraite
OverviewDiscussionsAdmin

Calculer une opération de marchand de biens

simulate_marchand_biens
Read-onlyIdempotent

Calcule le résultat d'une opération de marchand de biens : droits de mutation réduits avec engagement de revente (CGI art. 1115), impôt sur les sociétés au taux réduit et au taux normal, TVA sur marge (CGI art. 268) ou sur le prix total. Entrées : prix d'achat, travaux, prix de vente, régime de TVA, éligibilité au taux réduit. Sortie : frais, bénéfice, impôt, net. Calcul couvert par des cas 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": {
      "prixAchat": "<prixAchat>",
      "prixVente": "<prixVente>"
    },
    "name": "simulate_marchand_biens"
  }
}

Input Schema

NameRequiredDescriptionDefault
travauxNo
prixAchatYes
prixVenteYes
regimeTVANo
eligiblePMENo
autresChargesNo
sortieDividendeNo
engagementReventeNoDMTO réduit 0,715% si true (défaut true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds genuinely new behavioral context: the calculation is backed by 'cas de référence Marcel' and the output is explicitly 'indicatif', which tells the agent how much to trust the numbers — a caveat not present in any structured field.

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?

Three compact sentences: purpose and tax mechanics first, then inputs, then outputs, then the accuracy caveat. Dense but front-loaded and free of filler; the parenthetical legal citations are short and additive rather than padding.

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

Completeness3/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 does well to enumerate the return fields (frais, bénéfice, impôt, net). However, for an 8-parameter simulation at 13% schema coverage, three parameters and the TVA regime enum values remain opaque, which is a real gap for an agent assembling a correct call.

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 only 13%, so the description must carry the load. It does name five of the eight inputs (prix d'achat, travaux, prix de vente, régime de TVA, éligibilité au taux réduit), but leaves autresCharges, sortieDividende and the enum semantics of régimeTVA unexplained, so the compensation is partial.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a concrete verb and resource ('Calcule le résultat d'une opération de marchand de biens') and enumerates the fiscal mechanics covered (DMTO réduit, IS taux réduit/normal, TVA sur marge ou totale), plus the input and output fields. An agent can tell this is the marchand-de-biens scenario simulator rather than a generic property tool, though it never explicitly contrasts itself with siblings like simulate_pv_immo_ir or simulate_sci_ir_vs_is.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the domain vocabulary: an agent can infer it applies to a buy-renovate-resell professional operation, and the mention of 'engagement de revente' and 'éligibilité au taux réduit' hints at preconditions. There is no explicit when-to-use statement, no when-not-to-use, and no routing to alternatives among the many simulate_* siblings.

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