minimum-wage-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_minimum_wageA | Minimum wage for one US state or DC on a date in 2026-2027: standard hourly rate, tipped cash wage, tip credit and the date the rate took effect. Uses the US DOL July 2026 tables and state labor department pages checked October 2026, including increases on July 1, September 30 and January 1, 2027 that postdate most model training data. Applies the $7.25 federal floor when a state has no law or a lower rate, and says so. Inflation-indexed 2027 rates not yet published are reported as not announced, never estimated. State-level only: city and county rates are not included. |
| list_upcoming_increasesA | Every scheduled state minimum wage change from a date (default today) through 2027-12-31, sorted by date, with the new rate, the previous rate, the change and the tipped cash wage. Includes 2027-01-01 increases already enacted in law or announced under inflation indexing, and lists indexed changes whose number is not published yet as announced:false. Optional filter by states. |
| compare_statesA | Side-by-side minimum wages for 2 to 10 US states (or DC) on one date in 2026-2027: standard rate, tipped cash wage, tip credit, effective date and full-time annual pay (40 h x 52 weeks), sorted highest first, with the gap between highest and lowest. State-level only. |
| annual_income_at_minimum_wageA | Gross weekly, monthly and annual pay at a state's minimum wage on a date in 2026-2027, for given hours per week (default 40) and weeks per year (default 52). Uses the state rate in force on that date (with the federal floor where it applies). Pre-tax; ignores overtime and tips. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool targets a clearly distinct operation: single-state lookup, scheduled increases, multi-state comparison, and income calculation. There is no meaningful overlap, and the descriptions reinforce the boundaries (e.g., compare_states explicitly handles 2-10 states while get_minimum_wage handles one).
Three tools follow a clear verb_noun snake_case pattern (get_minimum_wage, list_upcoming_increases, compare_states). The fourth, annual_income_at_minimum_wage, is a descriptive noun phrase rather than a verb-led name, a minor deviation that remains readable and unambiguous.
Four tools is well-scoped for a focused minimum-wage dataset. Each tool serves a distinct query shape (single lookup, temporal listing, comparison, derived income) and none feels redundant or missing at this scale.
The surface covers lookup, forward-looking changes, comparison, and derived annual income, which addresses the core lifecycle for this domain. Minor gaps exist for broader use cases (e.g., historical rates, all-state listing beyond a 2-10 comparison, or locality-level data), but these are explicitly out of stated scope.