Planning

Lead-time guidance for an event

Use this when an agent wants to know whether TempGuru can typically staff an event at a given city and date, for example, 'is two weeks enough notice for Dallas?' Returns a recommendation in the set {yes, tight, rush, very-rush} based on the city's market tier and how far out the event is. This is planning guidance, not a real-time reservation. A confirmed booking requires a quote request at https://tempguru.co/get-staffing.

get/api/v1/availability

Request

  • Base URL: https://mcp.tempguru.co
  • URL: https://mcp.tempguru.co/api/v1/availability
  • Auth: none declared

Query parameters

citystring required

City name (e.g., 'Boston') or slug from /api/v1/cities (e.g., 'boston-event-staffing').

datestring date required

Event date in ISO format (YYYY-MM-DD).

rolestring

Optional role slug or name. When provided, the response also includes the rate range for that role in the resolved city.

headcountinteger

Optional headcount for the event. Echoed in the response so agents can include it in downstream quote requests.

Response

Availability guidance for the requested event.

inputobject required
city_foundtrue required
catalog_matchtrue required

The city resolved to a configured catalog entry; this does not confirm order coverage.

coverage_confirmation_requiredtrue required
citystring required
statestring required
city_tier'hub' | 'mid' | 'small' required
event_datestring date required
days_until_eventinteger required
in_pastboolean required

True when the requested event date has already passed. Confirm the intended date before planning or quoting.

typical_lead_time_hoursinteger required
recommendation'yes' | 'tight' | 'rush' | 'very-rush' required

yes = comfortable window; tight = at or near typical lead time; rush = inside lead time; very-rush = <24h.

role_foundboolean nullable required

null when no role was requested; true when the requested role resolved; false when it did not match the catalog.

countinteger nullable
notesstring[] required

Changes

No recorded changes to this operation across all 1 revision of this API.