macalc

calculate_cheque_repas

Calculate Belgian meal voucher (cheque-repas / maaltijdcheque) benefit. Returns: {face_value_per_voucher, employer_contribution_per_voucher, employee_contribution_per_voucher, monthly_total_vouchers, monthly_employer_cost, monthly_employee_contribution, ...}. See list_bundles for related 'finance-belgique' calculators.

Input Schema

TableJSON Schema

Name	Required	Description
`days_per_month`	No	Working days per month
`employee_contribution`	No	Employee contribution per voucher (min 1.09 EUR)
`employer_contribution`	No	Employer contribution per voucher (max 6.91 EUR)

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.

Changed1 schema field changedApr 25, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "formula": {
+      "description": "Human-readable formula or method used (e.g. \"I=P·r·t\", \"Magnus formula\").",
+      "type": "string"
+    },
+    "reference_url": {
+      "description": "Link to a calcul2 page documenting the calculation in detail.",
+      "type": "string"
+    },
+    "result": {
+      "description": "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": {
+      "description": "Authoritative source for the rule or formula (e.g. \"Article 197 CGI\", \"NF DTU 21\").",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedApr 8, 2026

TDQS

A3.6/5.0

Behavior2/5

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

No annotations provided; description only mentions calculation and return values. Lacks disclosure of side effects, permissions, or constraints beyond schema.

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 concise sentences front-load key info: purpose and output. 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?

With output schema and 3 simple numeric parameters, description is adequate for a straightforward calculator. Would benefit from hinting at Belgian regulatory context.

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 describes all 3 parameters with defaults and constraints (100% coverage). Description adds no extra meaning beyond listing output fields. 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?

Description specifies exact resource ('Belgian meal voucher (cheque-repas / maaltijdcheque) benefit') and verb ('Calculate') with explicit output fields, 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 Guidelines3/5

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

Mentions related 'list_bundles' for other calculators but no explicit when-to-use or when-not-to-use guidance. Usage context is implied by tool name.

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

All macalc 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.

Resources

Need Help?