Skip to main content
Glama

Calculate Unemployment Benefit

calculate_unemployment_benefit
Read-onlyIdempotent

Estimate French unemployment benefit (ARE — Aide au Retour a l'Emploi). Returns: {daily_ref_salary, daily_are, monthly_are_estimate, min_daily, max_daily_75pct_sjr}. See list_bundles for related 'finance-france' calculators.

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": {
      "daily_ref_salary": "<daily_ref_salary>"
    },
    "name": "calculate_unemployment_benefit"
  }
}

Input Schema

NameRequiredDescriptionDefault
daily_ref_salaryYesSalaire journalier de référence (SJR) in euros

Output Schema

NameRequiredDescriptionDefault
resultNoComputed result. Object whose fields depend on the tool (e.g. {tax, marginal_rate, brackets} for tax tools, {volume_l, gallons} for volume tools).
sourceNoAuthoritative source for the rule or formula (e.g. "Article 197 CGI", "NF DTU 21").
formulaNoHuman-readable formula or method used (e.g. "I=P·r·t", "Magnus formula").
reference_urlNoLink to a calcul2 page documenting the calculation in detail.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / daily_ref_salary / description
      Previous value: -"Salaire Journalier de Reference (SJR) in euros — typically last 12 months salary / 261"New value: +"Salaire journalier de référence (SJR) in euros"
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": false,
      +  "properties": {
      +    "formula": {
      +      "description": "Human-readable formula or method used (e.g. \"I=P·r·t\", \"Magnus formula\").",
      +      "type": "string"
      +    },
      +    "reference_url": {
      +      "description": "Link to a calcul2 page documenting the calculation in detail.",
      +      "type": "string"
      +    },
      +    "result": {
      +      "description": "Computed result. Object whose fields depend on the tool (e.g. {tax, marginal_rate, brackets} for tax tools, {volume_l, gallons} for volume tools)."
      +    },
      +    "source": {
      +      "description": "Authoritative source for the rule or formula (e.g. \"Article 197 CGI\", \"NF DTU 21\").",
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  3. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered without help. The description adds the framing that the result is an 'estimate' rather than an authoritative entitlement decision, which is useful, but it says nothing about rounding, applicability conditions, or limits of the formula.

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, front-loaded with the purpose and acronym expansion, followed by a short cross-reference. The enumerated return-field list is largely redundant with the existing output schema and is the one piece of text that does not fully earn its place.

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 simple one-parameter read-only calculator with a full output schema and complete annotations, the definition supplies purpose, the French-specific scope, and a related-bundle pointer — enough to call it correctly. Remaining gaps (eligibility assumptions, estimate precision) are minor for a pure calculation.

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 parameter is already documented as 'Salaire journalier de référence (SJR) in euros' with a non-negative minimum. The description adds no extra meaning about how SJR is computed or how it feeds the calculation, so baseline 3 applies.

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 gives a specific verb and resource: 'Estimate French unemployment benefit (ARE — Aide au Retour a l'Emploi)', and expands the acronym so the agent knows exactly which calculation is performed. It does not explicitly contrast with a sibling calculator, though the 'finance-france' bundle reference gives useful grouping context.

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 framing; there is no statement of when to pick this over another calculator, no note that the input must be a daily reference salary derived from prior employment, and no eligibility caveats. The pointer to list_bundles for related 'finance-france' calculators is the only routing guidance offered.

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