reference-data

check_minimum_wage

PAID ($0.05). Compliance verdict: is a salary at, above or below the country's statutory minimum wage? Returns verdict, margin, the statutory floor and the legal instrument it rests on. Honest statuses when no enforceable floor exists or the period doesn't match the floor's period (cross-period conversion is never guessed). Pass api_key if you have one; otherwise the response explains how to pay via x402.

Input Schema

TableJSON Schema

Name	Required	Description
`amount`	Yes	Wage to check, in the country's own currency
`period`	Yes	Period the amount covers — must match the statutory floor's period
`api_key`	No	API key (bypasses x402; metered for invoicing)
`country`	Yes	ISO country code

TDQS

A4.8/5.0

Behavior5/5

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

With no annotations, the description fully discloses that the tool is paid ($0.05), returns a verdict, margin, statutory floor, and legal instrument, and handles edge cases like missing floors or period mismatches honestly. No contradictions.

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 concise and well-structured, front-loading the tool's purpose and cost ('PAID ($0.05). Compliance verdict...'). Every sentence adds value, and no unnecessary words appear.

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?

Given no output schema, the description thoroughly explains what the tool returns (verdict, margin, floor, legal instrument) and addresses edge cases. With 4 parameters and 100% schema coverage, the description covers all necessary behavioral and constraint details for effective use.

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 coverage is 100%, but the description adds significant value beyond schema: it clarifies that amount is in the country's currency (schema says same), period must match statutory floor's period (schema only says 'Period the amount covers'), and api_key bypasses x402 with metered invoicing (schema merely says 'API key'). This enhances agent 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?

Description clearly states it checks if a salary meets the statutory minimum wage, using a specific verb ('compliance verdict') and resource ('statutory minimum wage'). It distinguishes from sibling tools like compute_income_tax or compute_vat, which deal with tax calculations.

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?

The description provides guidance on when to pass an api_key (if available) and explains that cross-period conversion is never guessed. It does not explicitly state when to use this tool versus alternatives, but the tool's purpose is clear enough for an agent to choose appropriately.

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 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

Need Help?