Skip to main content
Glama
tresor4k

macalc

calculate_swiss_vat

Convert between net (HT) and gross (TTC) amounts for Swiss invoices or expense reimbursements. Choose VAT rate (2.6%, 3.8%, 8.1%) and get tax amount.

Instructions

Compute Swiss VAT (TVA/MWST) — convert between net (HT) and gross (TTC). Use for invoicing or expense reimbursements in Switzerland. Inputs: amount, rate (8.1, 3.8, 2.6, 0). Returns HT, TTC, and tax amount. See list_bundles for related 'finance-suisse' calculators.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
amountYesAmount in CHF
rateNoVAT rate: 2.6% (reduced), 3.8% (hotel), 8.1% (standard)8.1
modeNoInput mode: ht=before tax, ttc=after taxht

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?

With no annotations, the description must convey behavior. It states the conversion and returns, but does not explicitly state that it is a read-only calculation with no side effects. The description adds value over the schema by mentioning output fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise (two sentences) and front-loaded with the core purpose. However, it contains an error regarding the rate values, which harms its reliability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers purpose, usage, inputs, and outputs. It is fairly complete for a simple calculator with an output schema. However, the error about the rate and the lack of explicit mention of the mode parameter reduce completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. However, the description includes a rate value '0' that is not in the schema enum (which only has 2.6, 3.8, 8.1), causing a discrepancy. It adds no extra semantics for the 'mode' parameter.

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 computes Swiss VAT, converts between net and gross, and lists use cases (invoicing, expense reimbursements). It distinguishes from siblings by specifying 'Swiss' and pointing to related 'finance-suisse' calculators.

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?

Explicit usage context is given ('invoicing or expense reimbursements in Switzerland') and a reference to related calculators is provided. Lacks explicit exclusions for other countries, but the context is clear.

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