Skip to main content
Glama

reference-data

by dev.euroref
OverviewDiscussionsAdmin

compute_income_tax

PAID ($0.05). Statutory income tax on a TAXABLE-income figure using the country's verified marginal bracket schedule, with full per-bracket workings, effective rate and marginal rate. Handles inflation-indexed tax units (Colombia UVT, Chile UTA, Peru UIT, Uruguay BPC) — you pass local currency. IMPORTANT: this is tax on taxable income, NOT net take-home pay — reliefs/allowances and social-security contributions are the caller's concern and are not applied (see the response scope_note). Pass api_key if you have one; otherwise the response explains how to pay via x402. Optional receipt (boolean, default false): on a paid success, include an Ed25519 answer receipt at no extra USDC. An answer receipt is not a series certified extract (GET /v1/certified/{country}/{series} is $0.25 and is not an MCP tool) and is not legal advice. Verify with verify_answer_receipt against /certified/public-key.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
api_keyNoAPI key (bypasses x402; metered for invoicing)
countryYesISO country code
receiptNoDefault false. When true, a paid success includes an Ed25519 answer receipt (kind answer_receipt) at no extra USDC. Unpaid 402 and free refusals do not include one. Not a series certified extract (GET /v1/certified/{country}/{series} at $0.25; that SKU is not an MCP tool).
taxable_incomeYesTaxable income in the country's local currency, in the schedule's own period basis (annual for most; monthly for Côte d'Ivoire, Uganda, Ethiopia, Costa Rica)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / receipt
      Added value: +{
+  "default": false,
+  "description": "Default false. When true, a paid success includes an Ed25519 answer receipt (kind answer_receipt) at no extra USDC. Unpaid 402 and free refusals do not include one. Not a series certified extract (GET /v1/certified/{country}/{series} at $0.25; that SKU is not an MCP tool).",
+  "type": "boolean"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / country / enum
      Previous value: -[
-  "at",
-  "be",
-  "bg",
-  "ch",
-  "cz",
-  "de",
-  "dk",
-  "ee",
-  "es",
-  "eu",
-  "fi",
-  "fr",
-  "gb",
-  "gr",
-  "hu",
-  "ie",
-  "is",
-  "it",
-  "lt",
-  "lv",
-  "nl",
-  "no",
-  "pl",
-  "pt",
-  "ro",
-  "rs",
-  "se",
-  "tr",
-  "ua"
-]New value: +[
+  "at",
+  "be",
+  "bg",
+  "ch",
+  "cy",
+  "cz",
+  "de",
+  "dk",
+  "ee",
+  "es",
+  "eu",
+  "fi",
+  "fr",
+  "gb",
+  "gr",
+  "hr",
+  "hu",
+  "ie",
+  "is",
+  "it",
+  "lt",
+  "lu",
+  "lv",
+  "mt",
+  "nl",
+  "no",
+  "pl",
+  "pt",
+  "ro",
+  "rs",
+  "se",
+  "si",
+  "sk",
+  "tr",
+  "ua"
+]
  3. Changed1 schema field changed
    • changedInput schema / properties / country / enum
      Previous value: -[
-  "at",
-  "be",
-  "bg",
-  "ch",
-  "cz",
-  "de",
-  "dk",
-  "es",
-  "eu",
-  "fi",
-  "fr",
-  "gb",
-  "gr",
-  "hu",
-  "ie",
-  "is",
-  "it",
-  "nl",
-  "no",
-  "pl",
-  "pt",
-  "ro",
-  "rs",
-  "se",
-  "tr",
-  "ua"
-]New value: +[
+  "at",
+  "be",
+  "bg",
+  "ch",
+  "cz",
+  "de",
+  "dk",
+  "ee",
+  "es",
+  "eu",
+  "fi",
+  "fr",
+  "gb",
+  "gr",
+  "hu",
+  "ie",
+  "is",
+  "it",
+  "lt",
+  "lv",
+  "nl",
+  "no",
+  "pl",
+  "pt",
+  "ro",
+  "rs",
+  "se",
+  "tr",
+  "ua"
+]
  4. Changed1 schema field changed
    • changedInput schema / properties / country / enum
      Previous value: -[
-  "at",
-  "be",
-  "bg",
-  "ch",
-  "cz",
-  "de",
-  "dk",
-  "es",
-  "fi",
-  "fr",
-  "gb",
-  "gr",
-  "hu",
-  "ie",
-  "is",
-  "it",
-  "nl",
-  "no",
-  "pl",
-  "pt",
-  "ro",
-  "rs",
-  "se",
-  "tr",
-  "ua"
-]New value: +[
+  "at",
+  "be",
+  "bg",
+  "ch",
+  "cz",
+  "de",
+  "dk",
+  "es",
+  "eu",
+  "fi",
+  "fr",
+  "gb",
+  "gr",
+  "hu",
+  "ie",
+  "is",
+  "it",
+  "nl",
+  "no",
+  "pl",
+  "pt",
+  "ro",
+  "rs",
+  "se",
+  "tr",
+  "ua"
+]
  5. Changed1 schema field changed
    • changedInput schema / properties / country / enum
      Previous value: -[
-  "at",
-  "be",
-  "ch",
-  "cz",
-  "de",
-  "dk",
-  "es",
-  "fi",
-  "fr",
-  "gb",
-  "gr",
-  "hu",
-  "ie",
-  "it",
-  "nl",
-  "no",
-  "pl",
-  "pt",
-  "ro",
-  "rs",
-  "se",
-  "tr"
-]New value: +[
+  "at",
+  "be",
+  "bg",
+  "ch",
+  "cz",
+  "de",
+  "dk",
+  "es",
+  "fi",
+  "fr",
+  "gb",
+  "gr",
+  "hu",
+  "ie",
+  "is",
+  "it",
+  "nl",
+  "no",
+  "pl",
+  "pt",
+  "ro",
+  "rs",
+  "se",
+  "tr",
+  "ua"
+]
  6. Changed1 schema field changed
    • changedInput schema / properties / country / enum
      Previous value: -[
-  "at",
-  "be",
-  "ch",
-  "cz",
-  "de",
-  "dk",
-  "es",
-  "fi",
-  "fr",
-  "gb",
-  "gr",
-  "hu",
-  "ie",
-  "it",
-  "nl",
-  "no",
-  "pl",
-  "pt",
-  "ro",
-  "se",
-  "tr"
-]New value: +[
+  "at",
+  "be",
+  "ch",
+  "cz",
+  "de",
+  "dk",
+  "es",
+  "fi",
+  "fr",
+  "gb",
+  "gr",
+  "hu",
+  "ie",
+  "it",
+  "nl",
+  "no",
+  "pl",
+  "pt",
+  "ro",
+  "rs",
+  "se",
+  "tr"
+]
  7. Changed1 schema field changed
    • changedInput schema / properties / country / enum
      Previous value: -[
-  "at",
-  "be",
-  "de",
-  "dk",
-  "es",
-  "fr",
-  "gb",
-  "ie",
-  "it",
-  "nl",
-  "pl",
-  "se"
-]New value: +[
+  "at",
+  "be",
+  "ch",
+  "cz",
+  "de",
+  "dk",
+  "es",
+  "fi",
+  "fr",
+  "gb",
+  "gr",
+  "hu",
+  "ie",
+  "it",
+  "nl",
+  "no",
+  "pl",
+  "pt",
+  "ro",
+  "se",
+  "tr"
+]
  8. Changed1 schema field changed
    • changedInput schema / properties / country / enum
      Previous value: -[
-  "de",
-  "es",
-  "fr",
-  "gb",
-  "it",
-  "nl"
-]New value: +[
+  "at",
+  "be",
+  "de",
+  "dk",
+  "es",
+  "fr",
+  "gb",
+  "ie",
+  "it",
+  "nl",
+  "pl",
+  "se"
+]
  9. First observed

TDQS

A4.8/5.0
Behavior5/5

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

No annotations exist, so the description fully carries behavioral disclosure. It reveals the $0.05 fee, x402 payment fallback, receipt behavior (optional, at no extra cost, not legal advice), and the scope_note in the response. It also discloses that reliefs/allowances are not applied. This is thorough for a computation tool.

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?

The description is dense but every sentence carries information: purpose, caveats, payment, receipt, verification. It is longer than average but appropriately so given the tool's complexity. Information is front-loaded (purpose and caveats before payment details). Not a model of brevity, but not wasteful.

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?

Covers the main computation, scope exclusions, payment, receipt, and verification route. With no output schema, it mentions per-bracket workings, effective and marginal rates, and the scope_note, which gives a good sense of the response. It does not explicitly describe error cases or exact response structure, but for a paid computation tool this is adequate.

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

Parameters5/5

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

Even though schema coverage is 100%, the description adds crucial meaning beyond the schema: taxable_income is clarified as local currency and period basis (annual vs monthly for specific countries), and the receipt boolean's behavior is explained in detail (what triggers it, what it is not). This materially improves parameter understanding.

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 statutory income tax on a taxable-income figure using marginal brackets, with per-bracket workings, effective and marginal rates. Differentiates from net take-home pay and mentions inflation-indexed units, distinguishing it from sibling tax tools like compute_vat and compute_employment_cost.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly warns it is tax on taxable income, not net pay, and that reliefs/allowances and social-security are caller's concern. Also contrasts with the certified extract SKU, giving clear when-not-to-use guidance and a specific alternative. No ambiguity about scope.

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

All reference-data toolsInspect
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