Skip to main content
Glama

BRAINIAC Pay, Tax & Employment Calendars

Look up US federal minimum wage

labour-tax_us-minimum-wage-lookup
Read-onlyIdempotent

Return the federal FLSA minimum wage for a date. State and local rates are not included in this slice. Price $0.02 USDC. POST /api/v1/labour-tax/us-minimum-wage-lookup. An unpaid call returns the x402 payment terms and does not run.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "asOf": "<asOf>"
    },
    "name": "labour-tax_us-minimum-wage-lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
asOfYesasOf, string, length 8 to 32. Required.
jurisdictionNojurisdiction, string, one of federal. Required.federal

Output Schema

NameRequiredDescriptionDefault
asOfNoasOf. String.
sourcesNosources. Array.
supportedNosupported. Boolean.
limitationsNolimitations. Array.
retrievedAtNoretrievedAt. String.
jurisdictionNojurisdiction. String.
effectiveFromNoeffectiveFrom. String.
hourlyRateUsdNohourlyRateUsd. Number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, open-world and non-destructive, so the safety profile is covered. Beyond that, the description discloses a priced operation ($0.02 USDC), the HTTP method and path, and the failure mode of unpaid calls (returns x402 payment terms without running). This is exactly the operational context an agent cannot get from annotations.

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?

Four short sentences, front-loaded with the purpose, then scope exclusion, price, endpoint, and payment behavior. Every sentence carries distinct information; nothing is repeated from the title or schema.

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?

With an output schema present, return values need not be described, and the definition covers cost, payment mechanics, and data scope. The only residual gap is date-format expectations for asOf, which the schema states only as a length range. For a two-parameter lookup this is close to complete.

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 the schema already documents both parameters and the single-value 'federal' enum. The phrase "for a date" loosely maps to asOf, but the description adds no format, timezone, or range guidance. Baseline 3 applies when the schema does the parameter work.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Return the federal FLSA minimum wage for a date" gives a specific verb (return), a specific resource (federal FLSA minimum wage), and a scope bound. The follow-up sentence explicitly excludes state and local rates, which narrows intent further. It does not, however, explicitly contrast with the closely related UK minimum-wage sibling, so it stops short of full sibling differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the correct use case (a dated US federal rate) and marks the boundary at state/local rates, hinting the caller needs another source. It also warns that an unpaid call only returns payment terms and does not execute, which is real invocation guidance. There is no explicit statement of when to prefer this over a sibling tool or what to do for sub-federal rates.

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