MaCalculatriceEnLigne

calculate_swiss_pillar3a

Calculate Swiss pillar 3a tax savings (3e pilier lie). Returns: {annual_contribution, net_cost_after_saving, max_employee_2026, max_self_employed_2026}. See list_bundles for related 'finance-suisse' calculators.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`marginal_tax_rate`	Yes	Marginal income tax rate in % (federal + cantonal combined)
`annual_contribution`	Yes	Annual contribution to pillar 3a in CHF (max 7056 for employees, 35280 for self-employed)

Output Schema

TableJSON Schema

Name	Required	Description
`result`	No	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`	No	Authoritative source for the rule or formula (e.g. "Article 197 CGI", "NF DTU 21").
`formula`	No	Human-readable formula or method used (e.g. "I=P·r·t", "Magnus formula").
`reference_url`	No	Link to a calcul2 page documenting the calculation in detail.

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 13, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations are provided, so the description must convey all behavioral information. It lists return fields and mentions limits (max_employee_2026, max_self_employed_2026) but does not explicitly state it is read-only, has no side effects, or discuss authorization. This is minimally sufficient but lacks explicit safety disclosure.

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 with no wasted words. First sentence covers purpose and return, second provides a hint for related tools. Extremely concise and front-loaded.

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 tool has only 2 parameters fully described in the schema and an output schema, the description is largely complete. However, it omits guidance on when to use this tool versus the many sibling calculators, and does not mention that the output schema defines the return structure. Still, it is sufficient for a simple calculation 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?

Since the input schema has 100% description coverage, the description adds no additional meaning beyond what the schema already provides. Baseline score of 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?

Description clearly states the tool calculates Swiss pillar 3a tax savings, names the specific resource ('pillar 3a' or '3e pilier'), and lists return fields. It also distinguishes itself from siblings by referencing related calculators in a bundle.

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?

No guidance on when to use this tool over alternatives. The mention of 'list_bundles' implies related calculators but does not specify conditions or context for this tool versus sibling Swiss tax calculators like 'calculate_swiss_income_tax'.

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

All MaCalculatriceEnLigne tools Inspect

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.