Skip to main content
Glama

reference-data

by dev.ausref

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

TDQS

A4.3/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. Discloses honest statuses for missing floors and period mismatches, explicitly states no cross-period guessing. Mentions payment method (x402) and api_key bypass. Does not detail rate limits or idempotency, but overall sufficiently transparent for a read-only check.

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?

Very concise—3 sentences cover purpose, behavior, edge cases, and payment. Front-loaded with key information. No redundant or vague wording.

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?

No output schema, yet description specifies return values: verdict, margin, statutory floor, legal instrument. Covers edge cases and payment flow. Given no annotations, this is a complete picture for an AI agent.

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 baseline 3. Description reinforces that period must match statutory floor's period, but does not add new semantic details beyond schema. No additional explanations for parameters like country codes or amount format.

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 explicitly states it provides a compliance verdict on whether a salary meets statutory minimum wage, using specific verb ('check' implied by name, 'returns verdict') and resource ('statutory minimum wage'). Clearly distinguishes 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?

Describes when to use (check salary against minimum wage) and mentions edge cases like no enforceable floor or period mismatch. States option to pass api_key or use x402 payment. No explicit 'when not to use', but context from sibling tools clarifies it's for minimum wage compliance.

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 domain: wage compliance, income tax, VAT, working days, holidays, series data (current, history, snapshot, catalog), and settlement dates. Even the financial computations (check_minimum_wage, compute_income_tax, compute_vat) have clearly different inputs and purposes, so no two tools are confusable.

Naming Consistency4/5

Most tools follow a clear verb_noun snake_case pattern (check_, compute_, count_, get_, list_). The only exception is `settlement_date`, which is a noun phrase rather than verb-first, but it remains consistent in style and readability. This minor deviation prevents a perfect score.

Tool Count5/5

With 10 tools, the server is well-scoped for a reference-data provider. It balances specific computations (minimum wage, tax, VAT) with general data access (series, holidays, settlements), and each tool serves a clear purpose without overlap or unnecessary bulk.

Completeness5/5

The tool surface comprehensively covers reference data for financial and calendar domains: statutory rates and compliance, holiday and working-day calendars, settlement conventions, and a generic series system with current, historical, snapshot, and catalog access. No obvious gaps impede an agent from accomplishing typical reference-data tasks, and the free list_series enables discovery.

Resources