TempGuru Event Staffing

Check Availability

check_availability

Read-only

Return tier-based lead-time guidance for an event date and configured market. Use for 'What's the typical lead time for brand ambassadors in [city]?' or 'Is this date inside the usual planning window?'. This is not a real-time inventory or order-coverage check: a TempGuru coordinator confirms coverage and final lead time for the specific order after buyer submission. DO NOT use for cost questions (use get_role_pricing) and never present the result as a reservation. check_availability(date='2026-08-14', city='Dallas') ; check_availability(date='2026-07-01', city='Boston', role='brand-ambassadors', count=6) Even a 'rush' window is worth submitting, same-week backfills exist in select markets.

Input Schema

TableJSON Schema

Name	Required	Description
`city`	Yes	City name (e.g., 'Boston') or slug (e.g., 'boston-event-staffing').
`date`	Yes	Event date as YYYY-MM-DD; legacy recognizable dates are still accepted.
`role`	No	Optional role name or slug to include rate context.
`count`	No	Optional headcount for the event.

Output Schema

TableJSON Schema

Name	Required	Description
`city`	No
`role`	No	Rate context when a role was provided; null otherwise.
`count`	No	Echo of the requested headcount.
`error`	No	Present when the date could not be parsed.
`notes`	No
`state`	No
`in_past`	No	True when the requested date is already in the past — confirm the date before planning.
`message`	No	Present when city_found is false.
`city_tier`	No	Market tier: hub = 25 major metros, mid = 128 secondary markets, small = 192 tertiary markets.
`requested`	No	Echo of the unmatched city input.
`city_found`	Yes	false = city did not match the configured catalog (see message); true = planning guidance below, not confirmed coverage.
`event_date`	No	Normalized ISO date (YYYY-MM-DD).
`role_found`	No	null = no role requested; false = the requested role didn't match the catalog (see notes).
`suggestion`	No	Closest known city/role for a miss. Confirm with the user before using it; do not auto-apply.
`catalog_match`	No
`recommendation`	No	Lead-time guidance, NOT a reservation. Even rush is worth submitting.
`role_suggestion`	No	Closest known city/role for a miss. Confirm with the user before using it; do not auto-apply.
`days_until_event`	No
`typical_lead_time_hours`	No
`coverage_confirmation_required`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedAug 10, 2026

addedOutput schema / properties / catalog_match

Added value: +{
+  "const": true,
+  "type": "boolean"
+}

changedOutput schema / properties / city_found / description

Previous value: -"false = city not in the published footprint (see message); true = guidance below."New value: +"false = city did not match the configured catalog (see message); true = planning guidance below, not confirmed coverage."

addedOutput schema / properties / coverage_confirmation_required
```
Added value: +{
+  "const": true,
+  "type": "boolean"
+}
```

Changed2 schema fields changedAug 8, 2026

changedInput schema / properties / date / description

Previous value: -"Event date in ISO format (YYYY-MM-DD) or any date string parseable by Date()."New value: +"Event date as YYYY-MM-DD; legacy recognizable dates are still accepted."

addedInput schema / properties / date / format
```
Added value: +"date"
```

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 15, 2026

changedOutput schema / properties / city_tier / description

Previous value: -"Market tier: hub = 25 major metros, mid = 129 secondary markets, small = 191 tertiary markets."New value: +"Market tier: hub = 25 major metros, mid = 128 secondary markets, small = 192 tertiary markets."

Changed4 schema fields changedJul 11, 2026

addedOutput schema / properties / in_past

Added value: +{
+  "description": "True when the requested date is already in the past — confirm the date before planning.",
+  "type": "boolean"
+}

addedOutput schema / properties / role_found

Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "null = no role requested; false = the requested role didn't match the catalog (see notes)."
+}

addedOutput schema / properties / role_suggestion

Added value: +{
+  "additionalProperties": false,
+  "description": "Closest known city/role for a miss. Confirm with the user before using it; do not auto-apply.",
+  "properties": {
+    "kind": {
+      "enum": [
+        "city",
+        "role"
+      ],
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    },
+    "slug": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "kind",
+    "slug",
+    "name"
+  ],
+  "type": "object"
+}

changedOutput schema / properties / suggestion / description

Previous value: -"Closest known city/role for a miss; retry with this slug."New value: +"Closest known city/role for a miss. Confirm with the user before using it; do not auto-apply."

Changed1 schema field changedJul 7, 2026

addedOutput schema / properties / suggestion

Added value: +{
+  "additionalProperties": false,
+  "description": "Closest known city/role for a miss; retry with this slug.",
+  "properties": {
+    "kind": {
+      "enum": [
+        "city",
+        "role"
+      ],
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    },
+    "slug": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "kind",
+    "slug",
+    "name"
+  ],
+  "type": "object"
+}

Changed1 schema field changedJun 10, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "city": {
+      "type": "string"
+    },
+    "city_found": {
+      "description": "false = city not in the published footprint (see message); true = guidance below.",
+      "type": "boolean"
+    },
+    "city_tier": {
+      "description": "Market tier: hub = 25 major metros, mid = 129 secondary markets, small = 191 tertiary markets.",
+      "enum": [
+        "hub",
+        "mid",
+        "small"
+      ],
+      "type": "string"
+    },
+    "count": {
+      "anyOf": [
+        {
+          "maximum": 9007199254740991,
+          "minimum": -9007199254740991,
+          "type": "integer"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Echo of the requested headcount."
+    },
+    "days_until_event": {
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "error": {
+      "description": "Present when the date could not be parsed.",
+      "type": "string"
+    },
+    "event_date": {
+      "description": "Normalized ISO date (YYYY-MM-DD).",
+      "type": "string"
+    },
+    "message": {
+      "description": "Present when city_found is false.",
+      "type": "string"
+    },
+    "notes": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "recommendation": {
+      "description": "Lead-time guidance, NOT a reservation. Even rush is worth submitting.",
+      "enum": [
+        "yes",
+        "tight",
+        "rush",
+        "very-rush"
+      ],
+      "type": "string"
+    },
+    "requested": {
+      "description": "Echo of the unmatched city input.",
+      "type": "string"
+    },
+    "role": {
+      "anyOf": [
+        {
+          "additionalProperties": false,
+          "properties": {
+            "all_inclusive": {
+              "type": "string"
+            },
+            "name": {
+              "type": "string"
+            },
+            "rate_range_usd": {
+              "additionalProperties": false,
+              "description": "All-inclusive hourly rate band (worker pay + payroll taxes + workers comp + liability).",
+              "properties": {
+                "high": {
+                  "description": "Upper end of the hourly rate range.",
+                  "type": "number"
+                },
+                "low": {
+                  "description": "Lower end of the hourly rate range.",
+                  "type": "number"
+                }
+              },
+              "required": [
+                "low",
+                "high"
+              ],
+              "type": "object"
+            }
+          },
+          "required": [
+            "name",
+            "rate_range_usd",
+            "all_inclusive"
+          ],
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Rate context when a role was provided; null otherwise."
+    },
+    "state": {
+      "type": "string"
+    },
+    "typical_lead_time_hours": {
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    }
+  },
+  "required": [
+    "city_found"
+  ],
+  "type": "object"
+}

First observedJun 4, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Despite annotations covering readOnly/non-destructive, the description adds valuable behavioral context: it clarifies the result is guidance, not a commitment; final coverage requires coordinator confirmation; and results must not be shown as reservations. This exceeds what annotations alone convey, even if it doesn't detail the output structure (which the output schema covers).

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

Conciseness5/5

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

The description is concise yet information-dense, with the core purpose front-loaded, followed by caveats, a 'DO NOT' that points to a sibling tool, and a strategic hint. Each sentence serves a clear function in guiding correct invocation.

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 the presence of an output schema, full parameter schema coverage, and behavior annotations, the description adds the right amount of extra context—tier-based, not a reservation, coordinator confirmation, and a useful market hint. The tool is well-specified for each aspect an agent needs to decide whether and how to call it.

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?

The input schema already covers all parameters with descriptions (100% coverage). The description adds useful examples demonstrating optional role and count but does not add deeper semantics beyond the schema. The schema handles the parameter documentation well.

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, distinct purpose: return tier-based lead-time guidance for an event date and configured market. It includes concrete example queries and explicitly differentiates itself from real-time inventory checks and cost queries (get_role_pricing), so an agent can clearly tell it apart from sibling tools.

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?

Provides explicit when-to-use guidance with natural language examples, explicit exclusions, and names the alternative tool for cost questions. It also includes a hint about rush windows and instructs the agent not to present the result as a reservation. This is thorough and actionable.

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.