Skip to main content
Glama

Lexou · droit français

Calculer une succession sans testament

calculer_succession
Read-onlyIdempotent

Dévolution légale d'une succession sans testament ni donation au dernier vivant : parts de chaque héritier (conjoint, enfants, parents, frères et sœurs), réserve et quotité disponible, valeur de l'usufruit (article 669 du CGI), droits de succession estimés après abattements. Pas pour une succession avec testament, ni à l'étranger.

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": {
      "actif_net": "<actif_net>",
      "conjoint": "<conjoint>",
      "enfants": "<enfants>",
      "enfants_tous_communs": "<enfants_tous_communs>",
      "parents": "<parents>",
      "freres_soeurs": "<freres_soeurs>"
    },
    "name": "calculer_succession"
  }
}

Input Schema

NameRequiredDescriptionDefault
enfantsYes
parentsYesNombre de parents du défunt encore en vie
conjointYes
actif_netYesActif net de succession, en euros
age_conjointNo
freres_soeursYes
option_conjointNoChoix de l'époux quand tous les enfants sont communs
donations_par_enfantNoDonations reçues par chaque enfant depuis moins de quinze ans
enfants_tous_communsYesTous les enfants sont-ils issus des deux époux ?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / parents / anyOf
      Added value: +[
      +  {
      +    "const": 0,
      +    "type": "number"
      +  },
      +  {
      +    "const": 1,
      +    "type": "number"
      +  },
      +  {
      +    "const": 2,
      +    "type": "number"
      +  }
      +]
    • removedInput schema / properties / parents / enum
      Removed value: -[
      -  0,
      -  1,
      -  2
      -]
    • removedInput schema / properties / parents / type
      Removed value: -"number"
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real value beyond that by disclosing what the computation produces: réserve/quotité split, usufruit valuation by article 669, and droits after abattements — important since there is no output schema. It does not mention precision, rounding, or that results are estimates subject to tax-authority rules beyond the word 'estimés'.

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: the computational content first, the exclusion last, with no filler or restatement of the title. The first sentence is dense with parenthetical lists, which costs some readability but every element maps to actual output or scope.

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?

For a 9-parameter, 6-required calculator with no output schema, the description covers both what is computed and the legal regime it applies to, which is the essential context. Remaining gaps are the meaning of the optional parameters (age_conjoint, option_conjoint, donations_par_enfant) and any note on result precision, but the schema types and enums carry much of that.

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 56%, so the description should compensate for the undocumented half but only partly does: it implies conjoint, enfants, parents and frères et sœurs through the heir list, and hints at usufruit valuation (which depends on age_conjoint) via the article 669 reference. It says nothing about actif_net, enfants_tous_communs, option_conjoint, or donations_par_enfant (the 'donation au dernier vivant' phrase refers to an excluded scenario, not the donation parameter), leaving those to the schema alone.

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 names a specific computation ('Dévolution légale d'une succession sans testament') and enumerates the concrete outputs: parts of each heir (conjoint, enfants, parents, frères et sœurs), réserve and quotité disponible, usufruit value under article 669 CGI, and estimated droits de succession after abattements. It also states its scope boundary ('sans testament ni donation au dernier vivant'), so an agent can distinguish it from any will-based or international estate tool without opening 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?

The exclusion clause 'Pas pour une succession avec testament, ni à l'étranger' gives explicit when-not guidance, which is the main routing risk for an estate calculator. It does not name an alternative tool for those cases, but no sibling in the provided list covers testate or foreign successions, so the omission is minor.

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