Skip to main content
Glama

reference-data

check_minimum_wage

Read-onlyIdempotent

PAID ($0.02). 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 (instant card checkout at /pricing); otherwise the response explains how to pay via x402. The evaluation country is free to try (see list_series). 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.10 and is not an MCP tool) and is not legal advice. Verify with verify_answer_receipt against /certified/public-key.

Input 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.10; that SKU is not an MCP tool).

Output Schema

NameRequiredDescriptionDefault
basisNo
errorNoPresent on a free refusal or error; no charge
floorNo
statusNoAnswer status, e.g. computed or an honest no-answer status
countryNo
receiptNoEd25519 answer receipt when receipt=true on a paid success
verdictNo
questionNo
no_chargeNo
price_usdNo
disclaimerNo
how_to_payNo
provenanceNoCited official sources behind the answer
bind_seriesNo
explanationNo
label_basisNoInputs and the rule ids that produced the two labels
x_next_bindNo
http_endpointNo
coverage_labelNoHow much of the question is covered: ready = complete; partial = held with a disclosed limitation or default; gap = no number served. Rules at /label-rules
confidence_labelNoEvidence verdict derived from source type, verification age and the stale flag (answers: the weakest series read). Rules at /label-rules
payment_requiredNotrue when the call needs payment; how_to_pay explains x402 or card

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / receipt / description
      Previous value: -"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)."New value: +"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.10; that SKU is not an MCP tool)."
    • removedOutput schema / properties / label_basis / properties / source_type / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / label_basis / properties / source_type / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / label_basis / properties / verification_age_days / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / label_basis / properties / verification_age_days / type
      Added value: +[
      +  "number",
      +  "null"
      +]
  2. Changed3 schema fields changed
    • addedOutput schema / properties / confidence_label
      Added value: +{
      +  "description": "Evidence verdict derived from source type, verification age and the stale flag (answers: the weakest series read). Rules at /label-rules",
      +  "enum": [
      +    "high",
      +    "medium",
      +    "low"
      +  ],
      +  "type": "string"
      +}
    • addedOutput schema / properties / coverage_label
      Added value: +{
      +  "description": "How much of the question is covered: ready = complete; partial = held with a disclosed limitation or default; gap = no number served. Rules at /label-rules",
      +  "enum": [
      +    "ready",
      +    "partial",
      +    "gap"
      +  ],
      +  "type": "string"
      +}
    • addedOutput schema / properties / label_basis
      Added value: +{
      +  "additionalProperties": {},
      +  "description": "Inputs and the rule ids that produced the two labels",
      +  "properties": {
      +    "confidence_reasons": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "coverage_reasons": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "inputs": {
      +      "items": {},
      +      "type": "array"
      +    },
      +    "rules": {
      +      "type": "string"
      +    },
      +    "rules_version": {
      +      "type": "string"
      +    },
      +    "source_type": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ]
      +    },
      +    "stale": {
      +      "type": "boolean"
      +    },
      +    "verification_age_days": {
      +      "anyOf": [
      +        {
      +          "type": "number"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ]
      +    }
      +  },
      +  "type": "object"
      +}
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": {},
      +  "description": "Minimum-wage compliance verdict",
      +  "properties": {
      +    "basis": {},
      +    "bind_series": {},
      +    "country": {
      +      "type": "string"
      +    },
      +    "disclaimer": {},
      +    "error": {
      +      "description": "Present on a free refusal or error; no charge"
      +    },
      +    "explanation": {},
      +    "floor": {},
      +    "how_to_pay": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "http_endpoint": {
      +      "type": "string"
      +    },
      +    "no_charge": {
      +      "type": "boolean"
      +    },
      +    "payment_required": {
      +      "description": "true when the call needs payment; how_to_pay explains x402 or card",
      +      "type": "boolean"
      +    },
      +    "price_usd": {
      +      "type": "number"
      +    },
      +    "provenance": {
      +      "description": "Cited official sources behind the answer"
      +    },
      +    "question": {},
      +    "receipt": {
      +      "description": "Ed25519 answer receipt when receipt=true on a paid success"
      +    },
      +    "status": {
      +      "description": "Answer status, e.g. computed or an honest no-answer status",
      +      "type": "string"
      +    },
      +    "verdict": {},
      +    "x_next_bind": {}
      +  },
      +  "type": "object"
      +}
  4. 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"
      +}
  5. Changed1 schema field changed
    • changedInput schema / properties / country / enum
      Previous value: -[
      -  "ar",
      -  "bb",
      -  "bo",
      -  "br",
      -  "bz",
      -  "cl",
      -  "co",
      -  "cr",
      -  "do",
      -  "ec",
      -  "gt",
      -  "hn",
      -  "jm",
      -  "mx",
      -  "ni",
      -  "pa",
      -  "pe",
      -  "py",
      -  "sv",
      -  "tt",
      -  "uy"
      -]New value: +[
      +  "ar",
      +  "bb",
      +  "bo",
      +  "br",
      +  "bz",
      +  "cl",
      +  "co",
      +  "cr",
      +  "do",
      +  "ec",
      +  "gt",
      +  "gy",
      +  "hn",
      +  "jm",
      +  "mx",
      +  "ni",
      +  "pa",
      +  "pe",
      +  "py",
      +  "sv",
      +  "tt",
      +  "uy"
      +]
  6. Changed1 schema field changed
    • changedInput schema / properties / country / enum
      Previous value: -[
      -  "ar",
      -  "bo",
      -  "br",
      -  "cl",
      -  "co",
      -  "cr",
      -  "do",
      -  "ec",
      -  "gt",
      -  "hn",
      -  "mx",
      -  "pa",
      -  "pe",
      -  "py",
      -  "sv",
      -  "uy"
      -]New value: +[
      +  "ar",
      +  "bb",
      +  "bo",
      +  "br",
      +  "bz",
      +  "cl",
      +  "co",
      +  "cr",
      +  "do",
      +  "ec",
      +  "gt",
      +  "hn",
      +  "jm",
      +  "mx",
      +  "ni",
      +  "pa",
      +  "pe",
      +  "py",
      +  "sv",
      +  "tt",
      +  "uy"
      +]
  7. Changed1 schema field changed
    • changedInput schema / properties / country / enum
      Previous value: -[
      -  "ar",
      -  "br",
      -  "cl",
      -  "co",
      -  "cr",
      -  "do",
      -  "ec",
      -  "gt",
      -  "mx",
      -  "pe",
      -  "py",
      -  "uy"
      -]New value: +[
      +  "ar",
      +  "bo",
      +  "br",
      +  "cl",
      +  "co",
      +  "cr",
      +  "do",
      +  "ec",
      +  "gt",
      +  "hn",
      +  "mx",
      +  "pa",
      +  "pe",
      +  "py",
      +  "sv",
      +  "uy"
      +]
  8. Added

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent/openWorld annotations: discloses the $0.02 cost, honest statuses when no enforceable floor exists, refusal to guess cross-period conversions, the receipt behavior (paid successes only), and that output is not legal advice. This is rich operational context an agent cannot infer from annotations alone.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Core purpose is front-loaded, but the description is long and dense, and the receipt/'certified extract is not an MCP tool' caveat is duplicated between the description and the receipt parameter's schema description. Some sentences could be trimmed without losing information.

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?

With an output schema present, return values need not be explained, and the description still covers everything else an agent needs: payment paths, receipt semantics, verification via verify_answer_receipt, and the legal caveat. Nothing material is missing.

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 real meaning: api_key bypasses x402 for instant checkout, and receipt is an optional boolean that yields an Ed25519 receipt only on paid successes. It clarifies behavior of parameters beyond their schema definitions.

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?

States a specific verb and resource (check a salary against statutory minimum wage) and describes the output (verdict, margin, statutory floor, legal instrument). It is clearly distinct from siblings like compute_employment_cost or compute_income_tax, which are different computations.

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?

Explains payment context (pass api_key, otherwise x402), points to list_series for the free evaluation country, and distinguishes this from the $0.10 certified extract SKU. However, it never explicitly states when to prefer this over sibling computation tools, so it stops short of full when/when-not guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources