Skip to main content
Glama

MaCalculatriceEnLigne

Calculate Senegalese Income Tax

calculate_senegalese_income_tax
Read-onlyIdempotent

Calculate Senegalese income tax (IR) on annual taxable income using the CGI Art. 173 progressive scale in XOF, before the family-charge reduction (Art. 174). Returns: {annual_income_xof, income_tax_xof, income_tax_capped_xof, effective_rate_pct, marginal_rate_pct, brackets}. See list_bundles for related 'finance-afrique-quebec' calculators.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "annual_income_xof": "<annual_income_xof>"
    },
    "name": "calculate_senegalese_income_tax"
  }
}

Input Schema

NameRequiredDescriptionDefault
annual_income_xofYesAnnual taxable income in XOF: gross minus the 30 % allowance capped at 900000

Output 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).
sourceNoAuthoritative source for the rule or formula (e.g. "Article 197 CGI", "NF DTU 21").
formulaNoHuman-readable formula or method used (e.g. "I=P·r·t", "Magnus formula").
reference_urlNoLink to a calcul2 page documenting the calculation in detail.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / annual_income_xof / description
      Previous value: -"Annual gross income in CFA Francs (XOF)"New value: +"Annual taxable income in XOF: gross minus the 30 % allowance capped at 900000"
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: which scale is applied, in which currency, and that the result is deliberately pre-Art. 174, which tells the agent what the number does and does not include.

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

Conciseness4/5

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

Two sentences, front-loaded with the core action, then the return fields, then the cross-reference. Dense but every clause carries information; the enumerated return keys are the only slightly redundant part given an output schema exists.

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?

The scope exclusions (pre-Art. 174, taxable rather than gross income) and the legal basis make it complete enough to call correctly, and an output schema exists so return values need not have been listed. Listing the return keys is mild duplication, leaving a small amount of headroom rather than a real gap.

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?

Only one parameter and schema description coverage is 100%, so the schema already documents it fully (annual income in XOF, 30% allowance capped at 900000). The description's phrase 'annual taxable income' confirms the input basis but adds no format or edge-case detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource (calculate Senegalese income tax / IR) plus the exact legal basis and scale (CGI Art. 173) and the currency (XOF). An agent can distinguish this from calculate_senegalese_vat and calculate_senegalese_css without opening any schema.

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?

Scopes the computation clearly as applying to annual taxable income on the progressive scale, and explicitly excludes the family-charge reduction of Art. 174, which signals when another complementary calculator would be needed. It also routes the agent to list_bundles for related finance calculators, though it does not name an alternative for the Art. 174 step itself.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.