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.4/5.0

Behavior4/5

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

No annotations provided, but description discloses it's a paid tool ($0.05), handles specific inflation-indexed units, and clarifies what it does not apply (reliefs/allowances, social security). Also mentions response includes scope_note and workings. Sufficient transparency for agent decision.

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?

Description is four sentences, front-loaded with purpose and cost. Efficient but could be more structured. However, no redundant information.

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?

No output schema, but description explains scope, inputs, limitations (not net pay, no reliefs), and response includes workings and scope_note. Adequate for agent to use correctly.

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?

Schema covers 100% parameters with descriptions. Description adds meaning: taxable_income is in local currency, period basis varies; api_key bypasses x402. Provides contextual value 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 statutory income tax on taxable income using marginal brackets, with full workings, effective rate, marginal rate, and handles inflation-indexed tax units. The verb 'compute' and resource 'income tax' are specific, and it distinguishes from siblings like compute_vat and check_minimum_wage.

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?

Provides important usage guidance: it's tax on taxable income, not net pay; reliefs/allowances are caller's concern; mentions api_key or x402 payment. Could offer more explicit when-to-use vs alternatives but given sibling tools, it's clear this is for income tax computation.

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.1/5.0

Disambiguation4/5

Most tools have clear, distinct purposes: minimum wage checking, income tax, VAT, working days, holidays, settlement dates, and generic series access all serve different functions. However, compute_vat and check_minimum_wage could be confused with simple get_series lookups for the same series (vat, minimum-wage), though the descriptions clarify that the compute_* tools provide breakdowns rather than just current values.

Naming Consistency4/5

The majority of tools follow a consistent verb_noun snake_case pattern (check_minimum_wage, compute_income_tax, compute_vat, count_working_days, get_public_holidays, get_series, get_series_history, get_snapshot, list_series). Settlement_date breaks the pattern as a noun-only name instead of something like get_settlement_date, creating a minor deviation.

Tool Count5/5

With 10 tools, the server is well-scoped for its reference-data purpose. It covers a broad but justified range of statutory and financial reference data without being excessive, and each tool serves a distinct function within that domain.

Completeness5/5

The tool set provides comprehensive coverage of typical reference data: minimum wage, income tax, VAT, public holidays, working days, settlement dates, and generic series with current values, history, and snapshots. The inclusion of list_series for discovery and the generic get_series/get_series_history endpoints cover the full lifecycle of accessing reference data. No obvious gaps for the stated purpose.

Resources

Need Help?