Skip to main content
Glama

Suxession — French Inheritance Tax Engine

by fr.suxession
OverviewDiscussionsAdmin

Teaser d'économie potentielle

estimer_economie_optimisation
Read-only

Estime le montant EXACT de l'économie potentielle via les 25 leviers d'optimisation (gratuit, même calcul que le site). Les leviers individuels ne sont jamais nommés ni chiffrés dans la réponse ; prix (99 €, paiement unique) et lien de paiement inclus. Les leviers détaillés sont révélés par explorer_optimisations après achat.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
situationYesSous-ensemble fiable du CalculRequest web (~30 sous-schemas → 8 champs). Cas simple uniquement : assurance-vie, donations, démembrement, SCI… → renvoi wizard.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • removedInput schema / properties / situation / $ref
      Removed value: -"#/$defs/SituationSimple"
    • addedInput schema / properties / situation / description
      Added value: +"Sous-ensemble fiable du CalculRequest web (~30 sous-schemas → 8 champs).\nCas simple uniquement : assurance-vie, donations, démembrement, SCI… → renvoi wizard."
    • addedInput schema / properties / situation / properties
      Added value: +{
+  "conjoint": {
+    "anyOf": [
+      {
+        "$ref": "#/$defs/ConjointMCP"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null,
+    "description": "Requis si situation_conjugale est marie ou pacse (âge du conjoint)"
+  },
+  "enfants": {
+    "items": {
+      "$ref": "#/$defs/EnfantMCP"
+    },
+    "maxItems": 15,
+    "title": "Enfants",
+    "type": "array"
+  },
+  "option_conjoint": {
+    "anyOf": [
+      {
+        "enum": [
+          "usufruit_total",
+          "quart_pleine_propriete",
+          "quart_pp_trois_quart_us"
+        ],
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null,
+    "description": "Uniquement pour marie — ignoré sinon",
+    "title": "Option Conjoint"
+  },
+  "parents_vivants": {
+    "anyOf": [
+      {
+        "enum": [
+          "deux",
+          "un",
+          "aucun"
+        ],
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null,
+    "title": "Parents Vivants"
+  },
+  "passif": {
+    "default": 0,
+    "description": "Dettes déductibles en euros",
+    "minimum": 0,
+    "title": "Passif",
+    "type": "number"
+  },
+  "patrimoine": {
+    "description": "Actif brut total en euros (immobilier, mobilier, liquidités)",
+    "exclusiveMinimum": 0,
+    "maximum": 1000000000,
+    "title": "Patrimoine",
+    "type": "number"
+  },
+  "regime_matrimonial": {
+    "anyOf": [
+      {
+        "enum": [
+          "communaute_legale",
+          "separation_de_biens",
+          "participation_aux_acquets",
+          "communaute_universelle"
+        ],
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null,
+    "description": "Uniquement pour marie/pacse — ignoré sinon",
+    "title": "Regime Matrimonial"
+  },
+  "situation_conjugale": {
+    "default": "celibataire",
+    "enum": [
+      "marie",
+      "pacse",
+      "concubin",
+      "celibataire",
+      "veuf",
+      "divorce"
+    ],
+    "title": "Situation Conjugale",
+    "type": "string"
+  }
+}
    • addedInput schema / properties / situation / required
      Added value: +[
+  "patrimoine"
+]
    • addedInput schema / properties / situation / title
      Added value: +"SituationSimple"
    • addedInput schema / properties / situation / type
      Added value: +"object"
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With readOnlyHint already covering safety, the description adds real behavioral context: individual levers are never named or quantified in the response, the price (99 €, one-time) and a payment link are included, and the calculation is free and identical to the site. This commercial/output disclosure is exactly the kind of thing annotations cannot express.

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 dense sentences, front-loaded with the core capability, then the output restriction, then the commercial terms and the sibling hand-off. No filler.

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 tool with annotations, a full input schema and an output schema, the description covers the essential unknowns: it is a teaser, levers stay hidden, and there is a paid unlock path. The simple-case-only limitation is carried by the schema, so nothing critical is missing.

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 100% and the single nested situation object is fully documented in the schema, so the baseline of 3 applies. The description adds no parameter syntax or constraint information beyond what the schema already provides.

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 (estime), resource (économie potentielle) and scope (25 leviers, calcul identique au site). It also distinguishes itself from the sibling explorer_optimisations by naming which tool reveals the detail.

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?

Makes clear this is the free teaser and that explorer_optimisations reveals details only after purchase, so the agent understands the teaser-vs-detail relationship. It does not explicitly state when to prefer it over comparer_scenarios or simuler_droits_succession, but the context is unambiguous.

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

All Suxession — French Inheritance Tax Engine 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