Skip to main content
Glama
tresor4k

macalc

calculate_senegalese_vat

Compute Senegalese VAT (TVA) for invoicing. Enter amount in XOF and select mode (HT or TTC). Returns HT, TTC, and tax amount. Uses standard 18% rate.

Instructions

Compute Senegalese VAT (TVA) — 18% standard rate. Use for invoicing in Senegal. Inputs: amount, mode (ht/ttc). Returns HT, TTC, tax amount. See list_bundles for related 'finance-afrique-quebec' calculators.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
amountYesAmount in XOF
rateNoTVA rate in % (standard 18%)
modeNoInput mode: ht=hors taxe, ttc=toutes taxes comprisesht

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?

Describes inputs and outputs (HT, TTC, tax amount) but does not disclose side effects or error cases. As a computation tool with no annotations, it provides adequate but not detailed behavioral context.

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, efficient and 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 present, return values are covered. Description includes standard rate and references related calculators. Sufficient for a simple VAT 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?

Schema has 100% coverage with descriptions. Description adds that amount is in XOF and mode values are ht/ttc, but adds little beyond schema. 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?

Explicitly states it computes Senegalese VAT at 18% standard rate for invoicing in Senegal. Distinguishes from siblings by specifying 'Senegalese' and mentioning related calculators via list_bundles.

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 states 'Use for invoicing in Senegal' and describes input modes (ht/ttc). Does not explicitly say when not to use or list alternatives, but the purpose is specific enough among siblings.

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