Skip to main content
Glama

reference-data

by dev.euroref
OverviewDiscussionsAdmin

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. Optional receipt (boolean, default false): on a paid success, include an Ed25519 answer receipt at no extra USDC. An answer receipt is not a series certified extract (GET /v1/certified/{country}/{series} is $0.25 and is not an MCP tool) and is not legal advice. Verify with verify_answer_receipt against /certified/public-key.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
amountYesWage to check, in the country's own currency
periodYesPeriod the amount covers — must match the statutory floor's period
api_keyNoAPI key (bypasses x402; metered for invoicing)
countryYesISO country code
receiptNoDefault false. When true, a paid success includes an Ed25519 answer receipt (kind answer_receipt) at no extra USDC. Unpaid 402 and free refusals do not include one. Not a series certified extract (GET /v1/certified/{country}/{series} at $0.25; that SKU is not an MCP tool).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / receipt
      Added value: +{
+  "default": false,
+  "description": "Default false. When true, a paid success includes an Ed25519 answer receipt (kind answer_receipt) at no extra USDC. Unpaid 402 and free refusals do not include one. Not a series certified extract (GET /v1/certified/{country}/{series} at $0.25; that SKU is not an MCP tool).",
+  "type": "boolean"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / country / enum
      Previous value: -[
-  "at",
-  "be",
-  "bg",
-  "ch",
-  "cz",
-  "de",
-  "dk",
-  "ee",
-  "es",
-  "eu",
-  "fi",
-  "fr",
-  "gb",
-  "gr",
-  "hu",
-  "ie",
-  "is",
-  "it",
-  "lt",
-  "lv",
-  "nl",
-  "no",
-  "pl",
-  "pt",
-  "ro",
-  "rs",
-  "se",
-  "tr",
-  "ua"
-]New value: +[
+  "at",
+  "be",
+  "bg",
+  "ch",
+  "cy",
+  "cz",
+  "de",
+  "dk",
+  "ee",
+  "es",
+  "eu",
+  "fi",
+  "fr",
+  "gb",
+  "gr",
+  "hr",
+  "hu",
+  "ie",
+  "is",
+  "it",
+  "lt",
+  "lu",
+  "lv",
+  "mt",
+  "nl",
+  "no",
+  "pl",
+  "pt",
+  "ro",
+  "rs",
+  "se",
+  "si",
+  "sk",
+  "tr",
+  "ua"
+]
  3. Changed1 schema field changed
    • changedInput schema / properties / country / enum
      Previous value: -[
-  "at",
-  "be",
-  "bg",
-  "ch",
-  "cz",
-  "de",
-  "dk",
-  "es",
-  "eu",
-  "fi",
-  "fr",
-  "gb",
-  "gr",
-  "hu",
-  "ie",
-  "is",
-  "it",
-  "nl",
-  "no",
-  "pl",
-  "pt",
-  "ro",
-  "rs",
-  "se",
-  "tr",
-  "ua"
-]New value: +[
+  "at",
+  "be",
+  "bg",
+  "ch",
+  "cz",
+  "de",
+  "dk",
+  "ee",
+  "es",
+  "eu",
+  "fi",
+  "fr",
+  "gb",
+  "gr",
+  "hu",
+  "ie",
+  "is",
+  "it",
+  "lt",
+  "lv",
+  "nl",
+  "no",
+  "pl",
+  "pt",
+  "ro",
+  "rs",
+  "se",
+  "tr",
+  "ua"
+]
  4. Changed1 schema field changed
    • changedInput schema / properties / country / enum
      Previous value: -[
-  "at",
-  "be",
-  "bg",
-  "ch",
-  "cz",
-  "de",
-  "dk",
-  "es",
-  "fi",
-  "fr",
-  "gb",
-  "gr",
-  "hu",
-  "ie",
-  "is",
-  "it",
-  "nl",
-  "no",
-  "pl",
-  "pt",
-  "ro",
-  "rs",
-  "se",
-  "tr",
-  "ua"
-]New value: +[
+  "at",
+  "be",
+  "bg",
+  "ch",
+  "cz",
+  "de",
+  "dk",
+  "es",
+  "eu",
+  "fi",
+  "fr",
+  "gb",
+  "gr",
+  "hu",
+  "ie",
+  "is",
+  "it",
+  "nl",
+  "no",
+  "pl",
+  "pt",
+  "ro",
+  "rs",
+  "se",
+  "tr",
+  "ua"
+]
  5. Changed1 schema field changed
    • changedInput schema / properties / country / enum
      Previous value: -[
-  "at",
-  "be",
-  "ch",
-  "cz",
-  "de",
-  "dk",
-  "es",
-  "fi",
-  "fr",
-  "gb",
-  "gr",
-  "hu",
-  "ie",
-  "it",
-  "nl",
-  "no",
-  "pl",
-  "pt",
-  "ro",
-  "rs",
-  "se",
-  "tr"
-]New value: +[
+  "at",
+  "be",
+  "bg",
+  "ch",
+  "cz",
+  "de",
+  "dk",
+  "es",
+  "fi",
+  "fr",
+  "gb",
+  "gr",
+  "hu",
+  "ie",
+  "is",
+  "it",
+  "nl",
+  "no",
+  "pl",
+  "pt",
+  "ro",
+  "rs",
+  "se",
+  "tr",
+  "ua"
+]
  6. Changed1 schema field changed
    • changedInput schema / properties / country / enum
      Previous value: -[
-  "at",
-  "be",
-  "ch",
-  "cz",
-  "de",
-  "dk",
-  "es",
-  "fi",
-  "fr",
-  "gb",
-  "gr",
-  "hu",
-  "ie",
-  "it",
-  "nl",
-  "no",
-  "pl",
-  "pt",
-  "ro",
-  "se",
-  "tr"
-]New value: +[
+  "at",
+  "be",
+  "ch",
+  "cz",
+  "de",
+  "dk",
+  "es",
+  "fi",
+  "fr",
+  "gb",
+  "gr",
+  "hu",
+  "ie",
+  "it",
+  "nl",
+  "no",
+  "pl",
+  "pt",
+  "ro",
+  "rs",
+  "se",
+  "tr"
+]
  7. Changed1 schema field changed
    • changedInput schema / properties / country / enum
      Previous value: -[
-  "at",
-  "be",
-  "de",
-  "dk",
-  "es",
-  "fr",
-  "gb",
-  "ie",
-  "it",
-  "nl",
-  "pl",
-  "se"
-]New value: +[
+  "at",
+  "be",
+  "ch",
+  "cz",
+  "de",
+  "dk",
+  "es",
+  "fi",
+  "fr",
+  "gb",
+  "gr",
+  "hu",
+  "ie",
+  "it",
+  "nl",
+  "no",
+  "pl",
+  "pt",
+  "ro",
+  "se",
+  "tr"
+]
  8. Changed1 schema field changed
    • changedInput schema / properties / country / enum
      Previous value: -[
-  "de",
-  "es",
-  "fr",
-  "gb",
-  "it",
-  "nl"
-]New value: +[
+  "at",
+  "be",
+  "de",
+  "dk",
+  "es",
+  "fr",
+  "gb",
+  "ie",
+  "it",
+  "nl",
+  "pl",
+  "se"
+]
  9. First observed

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description carries the full burden, and it does so thoroughly: it discloses the $0.05 paid cost, honest refusal statuses, that cross-period conversion is never guessed, and the exact receipt behavior. Even the distinction from the certified extract endpoint is made explicit.

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 dense but front-loaded: cost and purpose appear first, followed by return values, edge-case behavior, payment path, and receipt caveats. Every sentence adds distinct value, and the structure makes it easy to scan.

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?

For a paid tool with no output schema and no annotations, this is unusually complete: it covers required inputs, payment/auth, return fields, edge cases, receipt conditions, and how to verify the receipt. An agent has enough context to invoke it correctly.

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, but the description adds meaningful semantics beyond the schema: it explains that the period must match the statutory floor's period, that cross-period conversion is never guessed, and that receipts only appear on paid successes. This aids parameter selection beyond the field 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?

The description states a specific purpose: return a compliance verdict on whether a salary is at, above, or below the statutory minimum wage, with the margin, floor, and legal instrument. This clearly distinguishes it from computing taxes, employment costs, or public holidays.

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 gives clear context for when to use the tool: checking salary compliance against a country's minimum wage. It also explains the api_key/x402 payment path. It does not explicitly name sibling alternatives, but the purpose is specific enough that no exclusions are needed.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources