Skip to main content
Glama

Lexou · droit français

Calculer l'indemnité de rupture conventionnelle

calculer_indemnite_rupture_conventionnelle
Read-onlyIdempotent

Indemnité minimum de rupture conventionnelle avec le moteur officiel du Code du travail numérique : minimum légal et, si la convention collective est connue (IDCC), minimum conventionnel ; plus le calendrier daté (rétractation, homologation, fin du contrat au plus tôt). Si la convention pose une question, l'outil la renvoie : rappeler l'outil avec la réponse dans reponses_convention. Pas pour un licenciement ni pour un CDD.

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": {
      "profil": "<profil>",
      "date_entree": "<date_entree>",
      "date_signature": "<date_signature>",
      "salaire_brut_mensuel": "<salaire_brut_mensuel>"
    },
    "name": "calculer_indemnite_rupture_conventionnelle"
  }
}

Input Schema

NameRequiredDescriptionDefault
idccNoNuméro IDCC de la convention collective, si connu (Syntec : 1486)
profilYes
date_entreeYesDate d'entrée dans l'entreprise
alsace_moselleNo
date_signatureYesDate prévue de signature de la convention de rupture
salarie_protegeNo
primes_annuellesNoPrimes annuelles ou exceptionnelles des 12 derniers mois
reponses_conventionNoRéponses aux questions renvoyées par l'outil, sous la forme { nom_de_la_question : valeur }
salaire_brut_mensuelYesSalaire mensuel brut habituel, hors primes annuelles

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / reponses_convention / propertyNames
      Added value: +{
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful behavior: it returns both the legal minimum and the convention-based minimum, plus a dated calendar (rétractation, homologation, earliest contract end), and it can return questions requiring a follow-up call. It does not state what happens when idcc is unknown or how the question loop terminates.

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?

Front-loaded with the core output, then the follow-up mechanism, then the exclusions. Dense but every clause carries information; the single long opening sentence is the only mild readability cost.

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 9 parameters, a nested object and no output schema, the description does the important work of explaining what comes back (minimums plus a dated calendar) and how the interactive question loop works. Remaining gaps are the undocumented optional flags, which the schema partially covers.

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 67%, so the schema carries most of the load. The description adds meaning for idcc (convention collective triggers the convention-based minimum) and for reponses_convention (the answer map for returned questions), but says nothing about profil, salarie_protege, alsace_moselle or primes_annuelles beyond their schema text.

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 and resource ('Indemnité minimum de rupture conventionnelle') and explicitly scopes out adjacent cases: 'Pas pour un licenciement ni pour un CDD.' An agent can distinguish it from the sibling calculators 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?

Gives clear exclusions (licenciement, CDD) and describes the iterative usage pattern: if the convention raises a question, the tool returns it and must be re-called with the answer in reponses_convention. It does not name a specific alternative tool for the excluded cases, so it stops short of full routing guidance.

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