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.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`state`	Yes	Two-letter state code (e.g., 'CA') or full state name (e.g., 'California').

Output Schema

TableJSON Schema

Name	Required	Description
`state`	No
`w2_note`	No
`requested`	No
`state_abbr`	No
`state_found`	No	Present (false) only when the state didn't match.
`w2_required`	No
`data_version`	No	Version of the compliance dataset used for this result.
`min_wage_usd`	No	2026 state minimum wage.
`unique_rules`	No
`citation_note`	No	Operational guidance, not legal advice.
`currency_note`	No	Reminder that wages change annually; verify before relying.
`min_wage_as_of`	No	Effective date of this state's stored minimum wage.
`min_wage_source`	No	Authoritative source URL for the minimum wage figure.
`available_states`	No
`data_current_as_of`	No	Date the compliance dataset was last verified (YYYY-MM-DD).
`seventh_day_overtime`	No	True where a seventh-consecutive-day premium applies (CA).
`workers_comp_included`	No
`liability_coverage_included`	No
`overtime_daily_double_hours`	No	Start of the double-time band (hours/day) where the state has one (CA: 12); null otherwise.
`overtime_threshold_daily_hours`	No	Daily overtime threshold where the state has one (CA, AK, NV, CO); null otherwise.
`overtime_threshold_weekly_hours`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedJul 29, 2026

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"

Changed1 schema field changedJul 17, 2026

addedOutput schema / properties / data_version

Added value: +{
+  "description": "Version of the compliance dataset used for this result.",
+  "type": "string"
+}

Changed2 schema fields changedJul 11, 2026

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"
+}

Changed4 schema fields changedJul 7, 2026

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."
+}

Changed1 schema field changedJun 10, 2026

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"
+}

First observedJun 4, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already provide readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context beyond the annotations: it returns regulatory information, flags that it is not legal advice, and adds a daily-overtime hint (CA, AK, NV, CO). This is meaningful supplementary context.

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 description is front-loaded with the core purpose and return contents, followed by targeted usage examples, an explicit exclusion, and a useful hint. It is slightly verbose due to the example questions, but each part adds practical guidance, so the length is justified.

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 single-parameter read-only lookup with a rich schema, an output schema, and annotations already present, the description is complete. It covers what the tool returns, when to use it, when not to use it, the non-advice caveat, and an operational hint about daily-overtime states.

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% and the single 'state' parameter is already well described as accepting either a two-letter code or full state name. The description adds value with concrete example calls such as state='CA' and state='Tennessee', reinforcing accepted formats and making invocation unambiguous.

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?

The description states a specific verb and resource: 'Get the event staffing compliance summary for a US state', and lists what it returns (minimum wage, overtime rules, state-specific quirks). It also distinguishes itself from get_role_pricing by explicitly disclaiming rates, so an agent can clearly separate this tool from its siblings.

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?

The description gives concrete example questions that should trigger this tool, explicitly says 'DO NOT use for rates (use get_role_pricing)', and includes a 'NOT legal advice' caveat. This provides clear when-to-use and when-not-to-use guidance with a named alternative.

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

All TempGuru Event Staffing tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.