Skip to main content
Glama
tresor4k

macalc

calculate_senegalese_css

Calculate Senegalese CSS/IPRES social contributions for employee and employer based on gross monthly salary and work accident insurance rate.

Instructions

Calculate Senegalese social contributions (CSS/IPRES) for employee and employer. Returns: {gross_monthly_xof, employee, employer}. See list_bundles for related 'finance-afrique-quebec' calculators.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
gross_monthly_xofYesGross monthly salary in XOF
accident_rate_pctNoWork accident insurance rate 1-5% (employer only, default 3%)

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.
Behavior3/5

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

No annotations are provided, so the description must bear the burden. It states the tool calculates contributions and returns specified fields, but does not disclose safety traits (e.g., non-destructive) or side effects. It is adequate but not rich.

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?

The description is two sentences: one for purpose and return, one for pointing to related calculators. It is front-loaded, concise, and contains no superfluous information.

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?

Given the tool's simplicity (2 parameters, 1 required) and the presence of an output schema, the description covers purpose, basic return, and a pointer to related tools. It is complete for an agent to correctly invoke the tool.

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?

The input schema provides full description coverage (100%) for both parameters. The description adds no additional meaning beyond what is already in the schema, so baseline 3 is appropriate.

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 it calculates Senegalese social contributions (CSS/IPRES) for employee and employer, using a specific verb and resource. It distinguishes from siblings like calculate_senegalese_income_tax and calculate_senegalese_vat by focusing on social contributions.

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 provides no explicit guidance on when to use this tool versus alternatives. The mention of 'list_bundles' for related calculators is too indirect to serve as a usage guideline. There is no when-not or exclusion criteria.

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