Skip to main content
Glama
tresor4k

macalc

calculate_unemployment_benefit

Estimate French unemployment benefits (ARE) by entering your daily reference salary (SJR). Get daily and monthly payout estimates including minimum and maximum amounts.

Instructions

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daily_ref_salaryYesSalaire Journalier de Reference (SJR) in euros — typically last 12 months salary / 261

Output Schema

TableJSON 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).
formulaNoHuman-readable formula or method used (e.g. "I=P·r·t", "Magnus formula").
sourceNoAuthoritative source for the rule or formula (e.g. "Article 197 CGI", "NF DTU 21").
reference_urlNoLink to a calcul2 page documenting the calculation in detail.
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as safety (read-only, no side effects), authentication needs, or rate limits. The return fields are listed but not beyond that.

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?

Two sentences, front-loaded with purpose, then return fields and a pointer to related tools. No wasted words.

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?

Given the simplicity (one parameter, clear calculation), the description adequately covers purpose, output, and related resources. Minor missing: no disclaimer about estimate accuracy.

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 100%, and the parameter is already described in the schema. The description repeats the same context ('typically last 12 months salary / 261'), adding no extra value beyond the schema.

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 clearly states the tool estimates French unemployment benefit (ARE). It lists the return fields and points to related calculators, distinguishing it from siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description only hints at related tools via 'list_bundles' but does not explicitly state when to use this tool versus alternatives. No when-not-to-use or exclusion criteria provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tresor4k/macalc-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server