reference-data

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.

Input Schema

TableJSON Schema

Name	Required	Description
`api_key`	No	API key (bypasses x402; metered for invoicing)
`country`	Yes	ISO country code
`taxable_income`	Yes	Taxable 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)

TDQS

A4.9/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 transparency. It discloses the paid nature ($0.05), the exclusion of net take-home pay, the handling of inflation-indexed units, and the presence of a scope_note in the response. This gives a clear behavioral contract.

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?

The description is a single, well-organized paragraph that front-loads key information (paid, purpose) and efficiently conveys all necessary details without redundancy. Every sentence contributes meaning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite no output schema, the description effectively covers what the tool returns (per-bracket workings, effective rate, marginal rate) and limitations. It provides enough context for correct usage, including payment methods and parameter specifics.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description adds value by clarifying that taxable_income is in local currency and period basis as per the schedule, and that api_key is optional and bypasses x402. This enhances understanding beyond the 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?

The description clearly defines the tool's action: computing statutory income tax on taxable income using marginal bracket schedules. It distinguishes itself from sibling tools like compute_vat (indirect tax) by focusing on income tax. The specific mention of handling inflation-indexed tax units adds precision.

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 states when to use (for income tax on taxable income) and what it does not cover (reliefs, social security, net pay), directing responsibility to the caller. Also provides guidance on API key usage vs. x402 payment, aiding correct invocation.

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

All reference-data tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0

Disambiguation5/5

Each tool targets a distinct domain: wage compliance, income tax, VAT, working days, holidays, series data (current, history, snapshot, catalog), and settlement dates. Even the financial computations (check_minimum_wage, compute_income_tax, compute_vat) have clearly different inputs and purposes, so no two tools are confusable.

Naming Consistency4/5

Most tools follow a clear verb_noun snake_case pattern (check_, compute_, count_, get_, list_). The only exception is `settlement_date`, which is a noun phrase rather than verb-first, but it remains consistent in style and readability. This minor deviation prevents a perfect score.

Tool Count5/5

With 10 tools, the server is well-scoped for a reference-data provider. It balances specific computations (minimum wage, tax, VAT) with general data access (series, holidays, settlements), and each tool serves a clear purpose without overlap or unnecessary bulk.

Completeness5/5

The tool surface comprehensively covers reference data for financial and calendar domains: statutory rates and compliance, holiday and working-day calendars, settlement conventions, and a generic series system with current, historical, snapshot, and catalog access. No obvious gaps impede an agent from accomplishing typical reference-data tasks, and the free list_series enables discovery.

Resources

Need Help?