MaCalculatriceEnLigne

calculate_moroccan_vat

Compute Moroccan VAT (TVA) — convert between HT and TTC. Use for invoicing in Morocco. Inputs: amount, rate (20/14/10/7), mode (ht/ttc). Returns HT, TTC, tax amount. See list_bundles for related 'finance-afrique-quebec' calculators.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`mode`	No	Input mode: ht=hors taxe, ttc=toutes taxes comprises	ht
`rate`	No	VAT rate: 0%, 7%, 10%, 14%, or 20% (standard)	20
`amount`	Yes	Amount in MAD

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

A4.2/5.0

Behavior4/5

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

No annotations, so description carries full burden. It discloses inputs, conversion direction, and outputs. For a calculator, this is sufficient; no hidden side effects.

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, front-loaded with purpose, no wasted words. Extremely efficient.

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?

Description covers usage context and points to related tools. Output schema handles return values. Missing edge cases but acceptable for simple calculator.

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 coverage is 100% with descriptions. Description adds value by summarizing inputs and outputs (HT, TTC, tax amount) but does not significantly expand beyond schema.

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?

Clearly states it computes Moroccan VAT (TVA) converting between HT and TTC, distinct from generic or other country VAT tools. Describes inputs and outputs, making purpose unambiguous.

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?

Explicitly says 'Use for invoicing in Morocco' and directs to list_bundles for related calculators. Lacks explicit exclusion of non-Moroccan cases but context is clear.

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.