Skip to main content
Glama

reference-data

by dev.mearef

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
NameRequiredDescriptionDefault
api_keyNoAPI key (bypasses x402; metered for invoicing)
countryYesISO country code
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)

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, description carries full burden. It discloses the tool is paid ($0.05), handles inflation-indexed tax units, and specifies the scope (only taxable income). Response contents are outlined (per-bracket workings, effective rate, scope_note).

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 moderately concise, starting with price and core purpose. Key details and important note about net pay are front-loaded. Slightly long but every sentence adds value.

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 adequately describes return values (workings, rates, scope_note). Parameters are fully covered. Sibling tools are unrelated, so no missing context.

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 covers 100% of parameters, but description adds value: clarifies taxable_income is in local currency and period basis, and explains api_key bypasses x402 payment. This goes beyond schema descriptions.

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?

Description clearly states the tool computes statutory income tax on taxable income using marginal brackets. It uses specific verbs ('compute') and resource ('income tax'), and distinguishes itself 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?

Description explicitly notes this is tax on taxable income, not net take-home pay, and that reliefs/allowances are caller's concern. It also explains payment options (api_key or x402). No explicit alternatives but siblings are clearly different.

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
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 operation (check, compute, count, get, list) and a distinct resource (minimum wage, income tax, VAT, working days, holidays, series, settlement). The series tools are clearly differentiated by granularity (list, current, history, snapshot), and compute/check tools apply calculations rather than just returning values.

Naming Consistency4/5

Most tools follow a consistent verb_noun pattern (check_, compute_, count_, get_, list_), but settlement_date is a noun phrase without a verb, and the verbs vary (check, compute, count, get, list) rather than using a single style. Still, the names are descriptive and predictable.

Tool Count5/5

10 tools is within the ideal 3-15 range, and each tool earns its place by covering a distinct facet of statutory reference data: taxes, compliance checks, calendars, series, and settlement. There is no bloat or sense of missing essential tools.

Completeness4/5

The surface provides strong coverage: compliance checks (minimum wage, taxes), calendar operations (holidays, working days), series catalog/current/history/snapshot, and settlement dates. Minor gaps include no direct tool for settlement conventions (mentioned only as an external endpoint) and no standalone tax bracket getter, but get_series likely covers some rates and users can infer brackets from compute_income_tax.

Resources