Skip to main content
Glama

Lexou · droit français

Calculer la part saisissable d'un salaire

calculer_saisie_sur_salaire
Read-onlyIdempotent

Part saisissable d'une rémunération mensuelle nette selon le barème 2026 des articles R. 3252-2 et R. 3252-3 du Code du travail, majorée par personne à charge, en laissant toujours au salarié le montant forfaitaire du RSA. Rend les tranches et le montant mensuel saisissable. Pas pour une pension alimentaire (elle se prélève sans barème).

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": {
      "remuneration_nette_mensuelle": "<remuneration_nette_mensuelle>"
    },
    "name": "calculer_saisie_sur_salaire"
  }
}

Input Schema

NameRequiredDescriptionDefault
personnes_a_chargeNoNombre de personnes à charge
remuneration_nette_mensuelleYesRémunération nette mensuelle, en euros

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly/ idempotent/ non-destructive/ closed-world, so the safety profile needs no restating. The description goes further by disclosing the computation's substance: the 2026 barème, the per-dependant uplift, the mandatory RSA forfaitaire floor, and that it returns both tranches and the monthly seizable amount — context not derivable from annotations.

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?

One dense sentence front-loads the core definition and legal basis, followed by a short return-value clause and a compact exclusion. Every clause carries information; no filler or repetition of the title.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter, non-destructive calculation with no output schema, the definition supplies what an agent needs: the legal basis, the parameters' effects, the guaranteed floor, and an explicit statement of what is returned (tranches plus monthly seizable amount). Nothing material 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%, so both parameters are already documented, which sets the baseline at 3. The description adds moderate meaning by explaining that the amount is a net monthly figure and that it is 'majorée par personne à charge', clarifying the effect of the second parameter, but it gives no ranges, units beyond euros, or edge-case behavior.

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 ('Part saisissable d'une rémunération mensuelle nette') plus the exact legal basis (articles R. 3252-2 et R. 3252-3, barème 2026). It also explicitly marks the boundary with a look-alike use case ('Pas pour une pension alimentaire'), so an agent can tell it apart from other calculer_* tools.

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 when-to-use context (seizable portion of a net monthly salary under the barème, person-charge uplift, RSA floor preserved) and an explicit when-not with rationale ('pension alimentaire … se prélève sans barème'). It stops short of a perfect 5 only because it names no alternative tool or path for the excluded case.

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