Skip to main content
Glama

TempGuru Event Staffing

Get Compliance By State

get_compliance_by_state
Read-only

Get the event staffing compliance summary for a US state. Returns minimum wage, overtime rules, and state-specific quirks. Perfect for 'What are the W-2 vs 1099 rules for event workers in [state]?', 'What's the minimum wage for event staff in [state]?', or 'Are there compliance gotchas for hiring event workers in [state]?' questions. NOT legal advice, consult employment counsel for binding interpretation. DO NOT use for rates (use get_role_pricing). get_compliance_by_state(state='CA') ; get_compliance_by_state(state='Tennessee') Daily-overtime states (CA, AK, NV, CO) change shift budgeting, flag them in any plan.

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": {
      "state": "<state>"
    },
    "name": "get_compliance_by_state"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateYesTwo-letter state code (e.g., 'CA') or full state name (e.g., 'California').

Output Schema

NameRequiredDescriptionDefault
stateNo
w2_noteNo
requestedNo
state_abbrNo
state_foundNoPresent (false) only when the state didn't match.
w2_requiredNo
data_versionNoVersion of the compliance dataset used for this result.
min_wage_usdNo2026 state minimum wage.
unique_rulesNo
citation_noteNoOperational guidance, not legal advice.
currency_noteNoReminder that wages change annually; verify before relying.
min_wage_as_ofNoEffective date of this state's stored minimum wage.
min_wage_sourceNoAuthoritative source URL for the minimum wage figure.
available_statesNo
data_current_as_ofNoDate the compliance dataset was last verified (YYYY-MM-DD).
seventh_day_overtimeNoTrue where a seventh-consecutive-day premium applies (CA).
workers_comp_includedNo
liability_coverage_includedNo
overtime_daily_double_hoursNoStart of the double-time band (hours/day) where the state has one (CA: 12); null otherwise.
overtime_threshold_daily_hoursNoDaily overtime threshold where the state has one (CA, AK, NV, CO); null otherwise.
overtime_threshold_weekly_hoursNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedOutput schema / properties / min_wage_as_of / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / min_wage_as_of / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / min_wage_source / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / min_wage_source / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  2. Changed2 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. Changed1 schema field changed
    • addedOutput schema / properties / data_version
      Added value: +{
      +  "description": "Version of the compliance dataset used for this result.",
      +  "type": "string"
      +}
  4. Changed2 schema fields changed
    • addedOutput schema / properties / overtime_daily_double_hours
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maximum": 9007199254740991,
      +      "minimum": -9007199254740991,
      +      "type": "integer"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Start of the double-time band (hours/day) where the state has one (CA: 12); null otherwise."
      +}
    • addedOutput schema / properties / seventh_day_overtime
      Added value: +{
      +  "description": "True where a seventh-consecutive-day premium applies (CA).",
      +  "type": "boolean"
      +}
  5. Changed4 schema fields changed
    • addedOutput schema / properties / currency_note
      Added value: +{
      +  "description": "Reminder that wages change annually; verify before relying.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / data_current_as_of
      Added value: +{
      +  "description": "Date the compliance dataset was last verified (YYYY-MM-DD).",
      +  "type": "string"
      +}
    • addedOutput schema / properties / min_wage_as_of
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Effective date of this state's stored minimum wage."
      +}
    • addedOutput schema / properties / min_wage_source
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Authoritative source URL for the minimum wage figure."
      +}
  6. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": false,
      +  "properties": {
      +    "available_states": {
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "abbr": {
      +            "type": "string"
      +          },
      +          "name": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "abbr",
      +          "name"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "citation_note": {
      +      "description": "Operational guidance, not legal advice.",
      +      "type": "string"
      +    },
      +    "liability_coverage_included": {
      +      "type": "boolean"
      +    },
      +    "min_wage_usd": {
      +      "description": "2026 state minimum wage.",
      +      "type": "number"
      +    },
      +    "overtime_threshold_daily_hours": {
      +      "anyOf": [
      +        {
      +          "maximum": 9007199254740991,
      +          "minimum": -9007199254740991,
      +          "type": "integer"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "description": "Daily overtime threshold where the state has one (CA, AK, NV, CO); null otherwise."
      +    },
      +    "overtime_threshold_weekly_hours": {
      +      "maximum": 9007199254740991,
      +      "minimum": -9007199254740991,
      +      "type": "integer"
      +    },
      +    "requested": {
      +      "type": "string"
      +    },
      +    "state": {
      +      "type": "string"
      +    },
      +    "state_abbr": {
      +      "type": "string"
      +    },
      +    "state_found": {
      +      "const": false,
      +      "description": "Present (false) only when the state didn't match.",
      +      "type": "boolean"
      +    },
      +    "unique_rules": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "w2_note": {
      +      "type": "string"
      +    },
      +    "w2_required": {
      +      "type": "boolean"
      +    },
      +    "workers_comp_included": {
      +      "type": "boolean"
      +    }
      +  },
      +  "type": "object"
      +}
  7. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds genuinely useful context beyond that: a legal-advice disclaimer and a hint that daily-overtime states (CA, AK, NV, CO) change shift budgeting. It does not discuss error behavior for unrecognized states, keeping it short of a 5.

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

Conciseness4/5

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

The purpose and the sibling exclusion are front-loaded, and the disclaimer plus hint are short and on point. The three quoted example questions overlap with each other and with the purpose sentence, adding some length without much new 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?

For a one-parameter read tool with full schema coverage, complete annotations, and an output schema handling return values, the description covers purpose, alternatives, caveats, and a domain hint. Nothing an agent needs in order to call it correctly is missing.

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% and the single parameter already documents that either a two-letter code or a full name is accepted. The examples (state='CA', state='Tennessee') restate that same flexibility rather than adding new syntax, so the baseline 3 applies.

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+resource ('Get the event staffing compliance summary for a US state') and enumerates what is returned: minimum wage, overtime rules, state-specific quirks. It also explicitly routes away from the nearest sibling (get_role_pricing) for rate questions, so an agent can distinguish it without opening schemas.

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

Usage Guidelines5/5

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

Gives concrete trigger questions ('What are the W-2 vs 1099 rules...', minimum wage, compliance gotchas) and an explicit exclusion: 'DO NOT use for rates (use get_role_pricing)'. Both when-to-use and when-not-to-use are spelled out.

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.