Skip to main content
Glama
Sign In

MaCalculatriceEnLigne

by io.github.tresor4k
OverviewDiscussionsAdmin

Calculate Swiss Salary

calculate_swiss_salary
Read-onlyIdempotent

Convert Swiss gross monthly salary to estimated net salary after employee social contributions (AVS/AI/APG 5.3% uncapped, AC 1.1% up to 148,200/year, LPP employee share by age when age is given). Income tax and LAMal health insurance are not withheld. Same engine as /api/v1/salaire-net?pays=ch. Returns: {gross_monthly, avs_ai_apg_5_3pct, ac_chomage_1_1pct, lpp_2e_pilier_10pct (LPP employee share, CHF/month), lamal_health_fixed (0), net_monthly, ...}. See list_bundles for related 'finance-suisse' calculators.

Input Schema

NameRequiredDescriptionDefault
ageNoOptional age: adds the LPP employee contribution (ages 25-65); omitted = LPP not included
gross_monthlyYesGross monthly salary in CHF

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
    • addedInput schema / properties / age
      Added value: +{
+  "description": "Optional age: adds the LPP employee contribution (ages 25-65); omitted = LPP not included",
+  "maximum": 70,
+  "minimum": 17,
+  "type": "integer"
+}
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well past the readOnly/idempotent annotations by disclosing the exact contribution rates, the AC cap (148,200/year), the LPP age dependency, and explicit exclusions. It also notes it shares an engine with /api/v1/salaire-net?pays=ch, which tells the agent the result is an estimate, not a payroll-grade figure.

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 transform and its exclusions, with rates and return keys packed into a short block. The inline enumeration of return keys is somewhat verbose given an output schema exists, but no sentence is wasted.

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 read-only calculator, the description covers scope, formula inputs, exclusions, and shared-engine caveat; return fields are already covered by the output schema. An agent has everything needed to call it correctly and interpret the result.

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 in the schema, including age enabling LPP. The description restates the same age→LPP relationship and adds rate context but no new parameter syntax or format detail beyond the schema, so the baseline of 3 applies.

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 precise verb+resource (convert Swiss gross monthly salary to estimated net) and immediately scopes out what is NOT included. The mention that income tax and LAMal are excluded distinguishes it from siblings like calculate_swiss_income_tax without the agent needing to open either 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?

Clearly conveys the context of use (employee social contributions only, gross-to-net) and that age must be supplied for LPP to be included. It points to list_bundles for related calculators, but never names a direct alternative such as calculate_swiss_income_tax for the withheld-tax case, so routing is implied rather than explicit.

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

All MaCalculatriceEnLigne toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources