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

TDQS

A4.8/5.0

Behavior5/5

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

Annotations indicate readOnlyHint=true and destructiveHint=false; description adds that it returns compliance summary and is non-binding legal info, no contradictions. Provides context beyond annotations.

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?

Front-loaded with purpose, includes examples and hints. Slightly verbose but every sentence adds value. Could be trimmed slightly without loss.

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?

Given single parameter, existing output schema, and sibling tools, description fully covers usage, return details, and caveats. No gaps for this simple tool.

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%, but description adds concrete examples ('CA', 'Tennessee') illustrating the parameter, enhancing clarity beyond the schema description.

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 clearly states it retrieves 'event staffing compliance summary for a US state' with specific outputs (minimum wage, overtime rules, quirks), distinguishing it from siblings like get_role_pricing.

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?

Explicitly states when to use (questions about W-2/1099, minimum wage, compliance gotchas), when NOT to use ('DO NOT use for rates'), and directs to alternative get_role_pricing. Also includes legal disclaimer.

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

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.7/5.0

Disambiguation5/5

Each tool has a clearly distinct purpose with explicit do-not-use cross-references. Pricing tools (get_rate_benchmark vs get_role_pricing) are carefully separated, and plan_staffing vs check_availability serve different granularity needs.

Naming Consistency5/5

All tools use a consistent verb_noun snake_case pattern (get_cities, plan_staffing, request_quote). The verbs are simple and descriptive, with no mixed casing or stylistic inconsistencies.

Tool Count5/5

12 tools is well-scoped for an event staffing domain covering availability, pricing, roles, compliance, planning, persistence, and quote workflows. Each tool earns its place without redundancy.

Completeness4/5

The workflow is well-covered: plan_staffing creates plans, save/get manage persistence, request_quote hands off to a form, and get_quote_status tracks references. Minor gaps exist like lack of plan update/delete and quote status being a stub, but core operations are complete.

Get Compliance By State

Input Schema

Output Schema

TDQS

Glama MCP Gateway

TDQS

Resources