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

Behavior4/5

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

With no annotations, the description properly discloses the tool's behavior: returns verdict, margin, statutory floor, legal instrument, and honest statuses. It also mentions the x402 payment or api_key, adding transparency about how results are obtained.

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 concise with four sentences covering purpose, return values, edge cases, and payment. It is front-loaded with the verdict statement, though the structure could be slightly improved by separating core purpose from payment details.

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?

The tool has no output schema, but the description adequately explains return values (verdict, margin, floor, legal instrument) and handles edge cases (missing floor, period mismatch). It covers legal dependence, which is critical for compliance tools.

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

Parameters3/5

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

Schema coverage is 100%, so parameters are well-documented in the schema. The description only adds minor context (e.g., 'country's own currency' and period matching), but does not significantly enhance understanding beyond what the schema provides.

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 checks if a salary meets minimum wage and returns verdict, margin, floor, and legal instrument. The name 'check_minimum_wage' aligns perfectly, and it is distinct from sibling tools like compute_income_tax.

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 explains when the tool is honest about missing floors or period mismatches, and notes that cross-period conversion is never guessed. It does not explicitly list alternatives but implies when not to rely on it, which is adequate.

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?